From 9d0c6266a22841eb19080a0b54d1c52f85287018 Mon Sep 17 00:00:00 2001 From: tsteven4 <13596209+tsteven4@users.noreply.github.com> Date: Sun, 30 Oct 2022 11:17:28 -0600 Subject: [PATCH] update documentation to DocBook 5.0 (#940) * convert to docbook 5.0. * get jing running. * use uri to find docbook rng. * brew install jing-trang. use oasis for rngs. * add insertion markers to autogen doc files. * use db5-upgrade.xsl from docbook 5.1 release. we are still converting to docbook 5.0. this fixes issues with missing Appendix labels (e.g. "Appendix A. Supported Datums" was "Suppored Datums") and Glossary Indexes (e.g. "G" was omitted) in the html output. unfortunately it causes issues with translating ulinks inside term elements. We patch the dropped links back in. * make sure makedoc is using utf8 for files. --- .github/workflows/macos.yml | 1 + tools/Dockerfile_focal | 4 + tools/Dockerfile_jammy | 4 + tools/make_gpsbabel_html.sh | 3 +- tools/make_gpsbabel_org.sh | 2 +- tools/make_gpsbabel_pdf.sh | 2 +- xmldoc/babelmain.xsl | 2 +- xmldoc/babelpdf.xsl | 9 +- xmldoc/build.patch | 20 + xmldoc/chapters/build.xml | 42 +- xmldoc/chapters/datums.xml | 3 +- xmldoc/chapters/filters.xml | 4 +- xmldoc/chapters/formats.xml | 2 +- xmldoc/chapters/garmin_icons.xml | 2 +- xmldoc/chapters/glossary.xml | 34 +- xmldoc/chapters/preface.xml | 12 +- xmldoc/chapters/styles.xml | 517 +++++++++--------- xmldoc/chapters/use.xml | 80 +-- xmldoc/convertdoc | 76 +++ xmldoc/filters/arc.xml | 7 +- xmldoc/filters/bend.xml | 1 - xmldoc/filters/discard.xml | 5 +- xmldoc/filters/duplicate.xml | 3 +- xmldoc/filters/height.xml | 6 +- xmldoc/filters/interpolate.xml | 2 +- xmldoc/filters/nuketypes.xml | 3 +- xmldoc/filters/options/arc-distance.xml | 1 - xmldoc/filters/options/arc-exclude.xml | 1 - xmldoc/filters/options/arc-file.xml | 1 - xmldoc/filters/options/arc-points.xml | 1 - xmldoc/filters/options/bend-distance.xml | 2 - xmldoc/filters/options/bend-minangle.xml | 1 - xmldoc/filters/options/discard-elemax.xml | 1 - xmldoc/filters/options/discard-hdop.xml | 1 - xmldoc/filters/options/discard-matchcmt.xml | 1 - xmldoc/filters/options/discard-matchname.xml | 2 +- xmldoc/filters/options/discard-sat.xml | 1 - xmldoc/filters/options/discard-vdop.xml | 1 - xmldoc/filters/options/duplicate-all.xml | 3 +- xmldoc/filters/options/duplicate-correct.xml | 2 +- xmldoc/filters/options/duplicate-location.xml | 1 - .../filters/options/duplicate-shortname.xml | 2 - .../filters/options/interpolate-distance.xml | 1 - xmldoc/filters/options/interpolate-time.xml | 1 - xmldoc/filters/options/nuketypes-routes.xml | 1 - xmldoc/filters/options/nuketypes-tracks.xml | 1 - .../filters/options/nuketypes-waypoints.xml | 1 - xmldoc/filters/options/polygon-exclude.xml | 1 - xmldoc/filters/options/polygon-file.xml | 1 - xmldoc/filters/options/position-all.xml | 1 - xmldoc/filters/options/position-distance.xml | 1 - xmldoc/filters/options/radius-asroute.xml | 2 - xmldoc/filters/options/radius-maxcount.xml | 1 - xmldoc/filters/options/radius-nosort.xml | 1 - .../filters/options/simplify-crosstrack.xml | 1 - xmldoc/filters/options/stack-replace.xml | 1 - xmldoc/filters/options/stack-swap.xml | 1 - xmldoc/filters/options/track-course.xml | 1 - xmldoc/filters/options/track-discard.xml | 3 +- xmldoc/filters/options/track-faketime.xml | 4 +- xmldoc/filters/options/track-fix.xml | 1 - xmldoc/filters/options/track-merge.xml | 3 +- xmldoc/filters/options/track-move.xml | 7 +- xmldoc/filters/options/track-name.xml | 1 - xmldoc/filters/options/track-sdistance.xml | 2 - xmldoc/filters/options/track-start.xml | 2 +- xmldoc/filters/options/track-stop.xml | 1 - xmldoc/filters/options/transform-del.xml | 2 +- .../filters/options/transform-rptdigits.xml | 2 +- xmldoc/filters/options/transform-rptname.xml | 2 +- xmldoc/filters/options/transform-rte.xml | 2 +- xmldoc/filters/options/transform-trk.xml | 2 +- xmldoc/filters/options/transform-wpt.xml | 2 +- xmldoc/filters/polygon.xml | 9 +- xmldoc/filters/position.xml | 3 +- xmldoc/filters/radius.xml | 3 +- xmldoc/filters/resample.xml | 7 +- xmldoc/filters/reverse.xml | 1 - xmldoc/filters/simplify.xml | 1 - xmldoc/filters/sort.xml | 1 - xmldoc/filters/stack.xml | 1 - xmldoc/filters/track.xml | 2 - xmldoc/formats/baroiq.xml | 3 +- xmldoc/formats/cambridge.xml | 5 +- xmldoc/formats/csv.xml | 8 +- xmldoc/formats/custom.xml | 2 +- xmldoc/formats/dg-100.xml | 12 +- xmldoc/formats/dg-200.xml | 9 +- xmldoc/formats/exif.xml | 3 +- xmldoc/formats/garmin.xml | 18 +- xmldoc/formats/garmin301.xml | 8 +- xmldoc/formats/garmin_fit.xml | 6 +- xmldoc/formats/garmin_gpi.xml | 4 +- xmldoc/formats/garmin_poi.xml | 2 +- xmldoc/formats/garmin_txt.xml | 13 +- xmldoc/formats/gdb.xml | 5 +- xmldoc/formats/geojson.xml | 10 +- xmldoc/formats/globalsat.xml | 9 +- xmldoc/formats/gpsdrive.xml | 3 +- xmldoc/formats/gpsdrivetrack.xml | 1 - xmldoc/formats/gpssim.xml | 6 +- xmldoc/formats/gpx.xml | 7 +- xmldoc/formats/gtm.xml | 3 +- xmldoc/formats/gtrnctr.xml | 4 +- xmldoc/formats/holux.xml | 5 +- xmldoc/formats/html.xml | 1 - xmldoc/formats/humminbird.xml | 13 +- xmldoc/formats/iblue747.xml | 2 +- xmldoc/formats/iblue757.xml | 32 +- xmldoc/formats/igc.xml | 13 +- xmldoc/formats/kml.xml | 4 +- xmldoc/formats/lowranceusr.xml | 198 +++---- xmldoc/formats/m241-bin.xml | 2 +- xmldoc/formats/m241.xml | 4 +- xmldoc/formats/magellan.xml | 4 +- xmldoc/formats/magellan1.xml | 6 +- xmldoc/formats/magellanx.xml | 3 +- xmldoc/formats/miniHomer.xml | 12 +- xmldoc/formats/mtk-bin.xml | 7 +- xmldoc/formats/mtk.xml | 22 +- xmldoc/formats/navilink.xml | 12 +- xmldoc/formats/nmea.xml | 20 +- xmldoc/formats/openoffice.xml | 2 +- xmldoc/formats/options/exif-filename.xml | 1 - xmldoc/formats/options/exif-name.xml | 1 - .../formats/options/garmin-bitscategory.xml | 2 +- xmldoc/formats/options/garmin-deficon.xml | 3 +- xmldoc/formats/options/garmin_gpi-alerts.xml | 1 - .../options/garmin_gpi-languagecode.xml | 4 +- xmldoc/formats/options/garmin_gpi-notes.xml | 1 - .../formats/options/garmin_gpi-proximity.xml | 4 +- xmldoc/formats/options/garmin_gpi-speed.xml | 2 +- xmldoc/formats/options/garmin_gpi-unique.xml | 1 - xmldoc/formats/options/garmin_gpi-units.xml | 1 - xmldoc/formats/options/garmin_txt-datum.xml | 2 +- xmldoc/formats/options/garmin_txt-grid.xml | 4 +- xmldoc/formats/options/gdb-bitscategory.xml | 2 +- xmldoc/formats/options/gdb-dropwpt.xml | 1 - xmldoc/formats/options/gdb-roadbook.xml | 2 +- xmldoc/formats/options/gdb-via.xml | 1 - xmldoc/formats/options/geo-deficon.xml | 2 - xmldoc/formats/options/geo-nuke_placer.xml | 1 - xmldoc/formats/options/globalsat-showlist.xml | 2 +- xmldoc/formats/options/globalsat-track.xml | 2 +- xmldoc/formats/options/gpx-logpoint.xml | 2 +- xmldoc/formats/options/gpx-urlbase.xml | 1 - xmldoc/formats/options/igc-timeadj.xml | 2 - xmldoc/formats/options/kml-line_color.xml | 1 - xmldoc/formats/options/kml-points.xml | 1 - xmldoc/formats/options/m241-erase.xml | 1 - xmldoc/formats/options/miniHomer-Bar.xml | 3 +- xmldoc/formats/options/miniHomer-Boat.xml | 3 +- xmldoc/formats/options/miniHomer-Car.xml | 3 +- xmldoc/formats/options/miniHomer-Heart.xml | 3 +- xmldoc/formats/options/miniHomer-Home.xml | 3 +- xmldoc/formats/options/miniHomer-erase.xml | 1 - .../options/miniHomer-first-sector.xml | 2 +- xmldoc/formats/options/miniHomer-initbaud.xml | 1 - .../options/miniHomer-read-at-once.xml | 2 +- xmldoc/formats/options/nmea-date.xml | 2 - xmldoc/formats/options/nmea-gisteq.xml | 2 +- xmldoc/formats/options/nmea-gpgsa.xml | 1 - xmldoc/formats/options/nmea-gprmc.xml | 1 - xmldoc/formats/options/nmea-gpvtg.xml | 1 - xmldoc/formats/options/nmea-pause.xml | 1 - xmldoc/formats/options/nmea-snlen.xml | 1 - xmldoc/formats/options/osm-tag.xml | 2 +- xmldoc/formats/options/osm-tagnd.xml | 2 +- xmldoc/formats/options/ozi-altunit.xml | 1 - xmldoc/formats/options/skytraq-configlog.xml | 4 +- .../formats/options/skytraq-first-sector.xml | 2 +- .../options/skytraq-gps-utc-offset.xml | 2 +- .../options/skytraq-gps-week-rollover.xml | 2 +- .../formats/options/skytraq-read-at-once.xml | 2 +- .../options/skytraq-targetlocation.xml | 3 +- xmldoc/formats/options/subrip-format.xml | 2 +- xmldoc/formats/options/text-splitoutput.xml | 2 +- xmldoc/formats/options/tpg-datum.xml | 1 - xmldoc/formats/options/unicsv-datum.xml | 2 +- xmldoc/formats/options/unicsv-fields.xml | 2 +- xmldoc/formats/options/unicsv-filename.xml | 2 +- xmldoc/formats/options/unicsv-format.xml | 3 +- xmldoc/formats/options/unicsv-grid.xml | 2 +- xmldoc/formats/options/vcard-encrypt.xml | 1 - xmldoc/formats/options/xcsv-datum.xml | 2 +- xmldoc/formats/options/xcsv-snlen.xml | 1 - xmldoc/formats/options/xcsv-snunique.xml | 1 - xmldoc/formats/options/xcsv-snupper.xml | 1 - xmldoc/formats/options/xcsv-style.xml | 3 +- xmldoc/formats/osm.xml | 4 +- xmldoc/formats/sbn.xml | 6 +- xmldoc/formats/skytraq.xml | 8 +- xmldoc/formats/tabsep.xml | 3 +- xmldoc/formats/text.xml | 1 - xmldoc/formats/tpg.xml | 1 - xmldoc/formats/tpo2.xml | 2 - xmldoc/formats/tpo3.xml | 1 - xmldoc/formats/unicsv.xml | 22 +- xmldoc/formats/v900.xml | 9 +- xmldoc/formats/vcard.xml | 1 - xmldoc/formats/wbt-bin.xml | 9 +- xmldoc/formats/wbt-tk1.xml | 7 +- xmldoc/formats/wbt.xml | 14 +- xmldoc/formats/xcsv.xml | 1 - xmldoc/makedoc | 32 +- xmldoc/readme.xml | 11 +- xmldoc/tmissue.xsl | 11 + 207 files changed, 853 insertions(+), 865 deletions(-) create mode 100644 xmldoc/build.patch create mode 100755 xmldoc/convertdoc create mode 100644 xmldoc/tmissue.xsl diff --git a/.github/workflows/macos.yml b/.github/workflows/macos.yml index bf969be85..d734aac9a 100644 --- a/.github/workflows/macos.yml +++ b/.github/workflows/macos.yml @@ -61,6 +61,7 @@ jobs: brew update brew install ninja brew install docbook docbook-xsl fop gnu-sed + brew install jing-trang - name: Script env: diff --git a/tools/Dockerfile_focal b/tools/Dockerfile_focal index 11feada9b..c3ec82553 100644 --- a/tools/Dockerfile_focal +++ b/tools/Dockerfile_focal @@ -41,7 +41,11 @@ RUN apt-get update && apt-get install -y --no-install-recommends \ fop \ xsltproc \ docbook-xml \ + docbook5-xml \ docbook-xsl \ + docbook-xsl-ns \ + libavalon-framework-java \ + jing \ && rm -rf /var/lib/apt/lists/* # pkgs with libraries needed by gpsbabel diff --git a/tools/Dockerfile_jammy b/tools/Dockerfile_jammy index e1ac6f8f5..62214cf28 100644 --- a/tools/Dockerfile_jammy +++ b/tools/Dockerfile_jammy @@ -47,7 +47,11 @@ RUN apt-get update && apt-get install -y --no-install-recommends \ fop \ xsltproc \ docbook-xml \ + docbook5-xml \ docbook-xsl \ + docbook-xsl-ns \ + libavalon-framework-java \ + jing \ && rm -rf /var/lib/apt/lists/* # pkgs with libraries needed by gpsbabel diff --git a/tools/make_gpsbabel_html.sh b/tools/make_gpsbabel_html.sh index 4f4e66425..e0e9c802d 100755 --- a/tools/make_gpsbabel_html.sh +++ b/tools/make_gpsbabel_html.sh @@ -2,6 +2,7 @@ set -ex perl xmldoc/makedoc +jing http://docs.oasis-open.org/docbook/rng/5.0/docbook.rng xmldoc/readme.xml xsltproc \ --output gpsbabel.html \ --stringparam toc.section.depth "1" \ @@ -9,5 +10,5 @@ xsltproc \ --stringparam make.clean.html "1" \ --stringparam html.valid.html "1" \ --stringparam html.stylesheet "https://www.gpsbabel.org/style3.css" \ - http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl \ + http://docbook.sourceforge.net/release/xsl-ns/current/xhtml/docbook.xsl \ xmldoc/readme.xml diff --git a/tools/make_gpsbabel_org.sh b/tools/make_gpsbabel_org.sh index a49d9cbf6..2474d7df1 100755 --- a/tools/make_gpsbabel_org.sh +++ b/tools/make_gpsbabel_org.sh @@ -6,7 +6,7 @@ docversion=$2 mkdir -p "${web}/htmldoc-${docversion}" perl xmldoc/makedoc -xmllint --noout --valid xmldoc/readme.xml #valid and well-formed +jing http://docs.oasis-open.org/docbook/rng/5.0/docbook.rng xmldoc/readme.xml xsltproc \ --stringparam base.dir "${web}/htmldoc-${docversion}/" \ --stringparam root.filename "index" \ diff --git a/tools/make_gpsbabel_pdf.sh b/tools/make_gpsbabel_pdf.sh index d3a7316fa..bdd57abc2 100755 --- a/tools/make_gpsbabel_pdf.sh +++ b/tools/make_gpsbabel_pdf.sh @@ -2,6 +2,6 @@ set -ex perl xmldoc/makedoc -xmllint --noout --valid xmldoc/readme.xml #valid and well-formed +jing http://docs.oasis-open.org/docbook/rng/5.0/docbook.rng xmldoc/readme.xml xsltproc -o gpsbabel.fo xmldoc/babelpdf.xsl xmldoc/readme.xml HOME=. fop -q -fo gpsbabel.fo -pdf gpsbabel.pdf diff --git a/xmldoc/babelmain.xsl b/xmldoc/babelmain.xsl index cdac5934f..60eaa3322 100644 --- a/xmldoc/babelmain.xsl +++ b/xmldoc/babelmain.xsl @@ -4,7 +4,7 @@ exclude-result-prefixes="exsl"> - + 1 1 diff --git a/xmldoc/babelpdf.xsl b/xmldoc/babelpdf.xsl index 4d7125bd5..232da9d79 100644 --- a/xmldoc/babelpdf.xsl +++ b/xmldoc/babelpdf.xsl @@ -1,11 +1,12 @@ - + - + - + @@ -31,7 +32,7 @@ - + diff --git a/xmldoc/build.patch b/xmldoc/build.patch new file mode 100644 index 000000000..e3ba300d1 --- /dev/null +++ b/xmldoc/build.patch @@ -0,0 +1,20 @@ +--- chapters/build.xml.new 2022-10-27 09:44:25.567011354 -0600 ++++ chapters/build.xml 2022-10-27 09:49:05.876956001 -0600 +@@ -30,7 +30,7 @@ + + + +- Qt ++ Qt + + + +@@ -45,7 +45,7 @@ + + + +- libusb 1.0 ++ libusb 1.0 + + + diff --git a/xmldoc/chapters/build.xml b/xmldoc/chapters/build.xml index f0a6ee471..84348c41c 100644 --- a/xmldoc/chapters/build.xml +++ b/xmldoc/chapters/build.xml @@ -1,19 +1,19 @@ - + Getting or Building GPSBabel - +
Downloading - the easy way. GPSBabel is distributed "ready to run" on most common operating systems via the -download page. +download page. As GPSBabel runs on a wide variety of operating systems, be sure to visit the -OS-Specific notes for +OS-Specific notes for additional information. - - +
+
Building from source. For operating systems where no binary is provided, or if @@ -24,18 +24,18 @@ Less frequently, someone will build on FreeBSD, OpenBSD, Solaris, etc. Clang/LLVM, GNU C++, and MSVC are regularly exercised via automation. -You can grab a release from the GPSBabel download page, but if you're going to be doing any development, you'll find that working from the GPSBabel Github repo is easier. Checkouts via Git, HTTPS, SSH, and Subversion are supported. +You can grab a release from the GPSBabel download page, but if you're going to be doing any development, you'll find that working from the GPSBabel Github repo is easier. Checkouts via Git, HTTPS, SSH, and Subversion are supported. There are external requirements for bulding. - Qt + Qt Qt version 5.12 or newer is required for all builds. MacOS and Windows users can download -binaries from Qt Downloads +binaries from Qt Downloads Fedora or CentOS users may need to 'dnf install qt5-qtbase-devel'. When in doubt, 'dnf search qt' or 'dnf search qt5' may help you find the correct package name. Ubuntu users may need to 'apt-get install qt5-default'. Package names and versions in Linux frequently change, so you may need to ask your Linux vendor for help or look in tools/Docker* for inspiration for our automated builds that @@ -45,7 +45,7 @@ use Docker. - libusb 1.0 + libusb 1.0 @@ -57,7 +57,7 @@ from our automated Docker builds. - +
Brief history of internals Parts of GPSBabel have been public since 2002, with some of the original @@ -71,25 +71,25 @@ from our automated Docker builds. not enforced style rules as strongly across modules as we could have. Fixing both of these is a goal for us in 2020. - - +
+
Building with Qt Creator Qt provides a lovely IDE (Integrated Development Evironment) with an editor and debugger. Its use is strongly encouraged for those new to C++. Once you have Qt correctly installed, just opening the CMakeLists.txt from -the File->Open menu in an already-running instance of Qt Creator is the fastest and easiest way for most +the File->Open menu in an already-running instance of Qt Creator is the fastest and easiest way for most people to get to development because it handles things like build dependencies changing and class and method compilation. A path of low resistance for some users is to use the CMakeLists.txt file -from the command line. If you type cmake . in our working +from the command line. If you type cmake . in our working directory it will create a buildsystem with the default generator (Unix Makefiles or Visual Studio) which you can use for development. - - +
+
Building from the command line Those familiar with the command line may be more comfortable using cmake from the command line. @@ -365,8 +365,8 @@ installer will be created gui/Setup-x.y.z-Setup.exe. - - +
+
Runtime Dependencies: On non-macOS unix builds by default we now compile in the gpsbabel generated @@ -376,6 +376,6 @@ These are used by the GUI. Additional translation files from Qt will also be used if they are found. They may be in a package such as qttranslations5-l10n or qt5-qttranslations. - - +
+
diff --git a/xmldoc/chapters/datums.xml b/xmldoc/chapters/datums.xml index 24ea17038..8c8cc6d40 100644 --- a/xmldoc/chapters/datums.xml +++ b/xmldoc/chapters/datums.xml @@ -1,4 +1,4 @@ - + Supported Datums Some formats in GPSBabel support multiple datums. For example, the @@ -135,4 +135,3 @@ The following is a list of the datums supported by GPSBabel. Sweden - diff --git a/xmldoc/chapters/filters.xml b/xmldoc/chapters/filters.xml index e3225a28c..939568ac1 100644 --- a/xmldoc/chapters/filters.xml +++ b/xmldoc/chapters/filters.xml @@ -1,4 +1,4 @@ - + Data Filters GPSBabel supports data filtering. Data filters are invoked from the command line via the '-x' option. It should be @@ -16,7 +16,7 @@ Beware that most filters only apply to a certain kind of data. This is usually indicated below by referring to points, tracks or routes in the first sentence which describes each - filter or in the table at gpsbabel.org + filter or in the table at gpsbabel.org . &filters; diff --git a/xmldoc/chapters/formats.xml b/xmldoc/chapters/formats.xml index a06e0be6b..be52f2dc1 100644 --- a/xmldoc/chapters/formats.xml +++ b/xmldoc/chapters/formats.xml @@ -1,4 +1,4 @@ - + The Formats &formats; diff --git a/xmldoc/chapters/garmin_icons.xml b/xmldoc/chapters/garmin_icons.xml index 898310470..e0b393e6f 100644 --- a/xmldoc/chapters/garmin_icons.xml +++ b/xmldoc/chapters/garmin_icons.xml @@ -1,4 +1,4 @@ - + Garmin Icons Following is a list of the valid values for the diff --git a/xmldoc/chapters/glossary.xml b/xmldoc/chapters/glossary.xml index 9d02a1eda..7e75e0f9f 100644 --- a/xmldoc/chapters/glossary.xml +++ b/xmldoc/chapters/glossary.xml @@ -1,29 +1,29 @@ - + Glossary Terms that are used in conjunction with GPSBabel. - + G - + Geocaching - GPS based "paper chase", see + GPS based "paper chase", see - + http://en.wikipedia.org/wiki/Geocaching I - + Itinerary same as a Route (e.g. used by TomTom) - + P - + Points of Interest (POI) a collection of gas stations, post boxes, shops and @@ -31,9 +31,9 @@ - + R - + Route a list of geopoints (often with names) connected in @@ -41,17 +41,17 @@ defining the route you want to pass while traveling, created by PC software, or generated inside a GPS device. They can be composed of existing waypoints, or new - "routepoints" might be generated. + "routepoints" might be generated. - + T - + Track a collection of geopoints recorded by your GPS - device while traveling -- "breadcrumb trails". The order + device while traveling -- "breadcrumb trails". The order of trackpoints within the track is important. Usually a trackpoint doesn't have a name or comment, but a timestamp. This distinguishes a trackpoint from a @@ -59,9 +59,9 @@ - + W - + Waypoints are geopoints that are not necessarily connected to @@ -73,4 +73,4 @@ - \ No newline at end of file + diff --git a/xmldoc/chapters/preface.xml b/xmldoc/chapters/preface.xml index 695355d5f..339b14e29 100644 --- a/xmldoc/chapters/preface.xml +++ b/xmldoc/chapters/preface.xml @@ -1,12 +1,12 @@ - + Introduction to GPSBabel -
+
The Problem: Too many incompatible GPS file formats There are simply too many gratuitously different file formats to hold waypoint, track, and route information in various programs used by computers and GPS receivers. - GPX + GPX defines a standard in XML to contain all the data, but there are too many programs that don't understand it yet and too much data in @@ -26,14 +26,14 @@ is a program that converts data between the two programs. GPSBabel actually solves that problem for you and much more...
-
+
The Solution The original author of GPSBabel, - Robert Lipe + Robert Lipe , needed to convert waypoints between a couple of formats, so he whipped up a converter and designed it upon an extensible foundation so that it was easy to add new formats and made the program freely available. - Many others + Many others have contributed to the program since then. Most file formats added so far have taken under 200 lines of reasonable ISO C so they can be stamped diff --git a/xmldoc/chapters/styles.xml b/xmldoc/chapters/styles.xml index 49c21cf02..2fa789a9b 100644 --- a/xmldoc/chapters/styles.xml +++ b/xmldoc/chapters/styles.xml @@ -1,8 +1,8 @@ - + GPSBabel XCSV Style Files -
+
Introduction to GPSBabel Styles - Often it is desirable to add a new file format for "one-off" work (perhaps + Often it is desirable to add a new file format for "one-off" work (perhaps you want to export something to a spreadsheet or graphing program) or to read a format that GPSBabel does not yet support. For suitably simple formats, this can be done by a user with no programming experience by providing a @@ -21,8 +21,8 @@ are not good fits for this scheme. It should have: Once you have created a style file that describes the file format you have or want, you must tell GPSBabel to use the xcsv format and have the xcsv format use that file. If you created a new style file called -"mystyle.style" and you want to write the waypoints from -a GPX file named "mine.gpx" to it, you would issue a command like: +"mystyle.style" and you want to write the waypoints from +a GPX file named "mine.gpx" to it, you would issue a command like: gpsbabel -i gpx -f mine.gpx -o xcsv,style=mystyle.style -F mine.new @@ -48,12 +48,12 @@ then share Send it along with a coherent description to the GPSBabel-Misc mailing list for consideration to be included in a future version.
-
+
Style file overview The first and foremost important step is understanding how the style file is laid out itself. The format is: - DIRECTIVE<whitespace>VALUE + DIRECTIVE<whitespace>VALUE Where <whitespace> is one or more spaces or tabs. There should be no spaces or tabs at the beginning of the line; all directives start at the left edge in column zero. @@ -79,7 +79,7 @@ EXTENSION txt # FIELD_DELIMITER TAB RECORD_DELIMITER NEWLINE -BADCHARS ," +BADCHARS ," PROLOGUE Name Latitude Longitude Description URL Type Container Diff Terr @@ -89,20 +89,20 @@ PROLOGUE Name Latitude Longitude Description URL Type Container Diff Te # EXPORT THIS ANYWHERE SO WE CAN HAVE OUR # WAY WITH THE FORMATTING. # -IFIELD SHORTNAME, "", "%s" # Name -IFIELD LAT_DECIMAL, "", "%f" # Latitude -IFIELD LON_DECIMAL, "", "%f" # Longitude -IFIELD DESCRIPTION, "", "%s" # Name 2 (Big Description) -IFIELD URL, "", "%s" # URL -IFIELD GEOCACHE_TYPE, "", "%s" # Geocache Type -IFIELD GEOCACHE_CONTAINER, "", "%s" # Geocache Type -IFIELD GEOCACHE_DIFF, "", "%3.1f" # Geocache Type -IFIELD GEOCACHE_TERR, "", "%3.1f" # Geocache Type +IFIELD SHORTNAME, "", "%s" # Name +IFIELD LAT_DECIMAL, "", "%f" # Latitude +IFIELD LON_DECIMAL, "", "%f" # Longitude +IFIELD DESCRIPTION, "", "%s" # Name 2 (Big Description) +IFIELD URL, "", "%s" # URL +IFIELD GEOCACHE_TYPE, "", "%s" # Geocache Type +IFIELD GEOCACHE_CONTAINER, "", "%s" # Geocache Type +IFIELD GEOCACHE_DIFF, "", "%3.1f" # Geocache Type +IFIELD GEOCACHE_TERR, "", "%3.1f" # Geocache Type Each of these lines will be explained in the following sections.
-
+
Internal Constants A few internal constants are defined in the XCSV parser to make the style file simpler. They may or may not be used and are optional in most cases. @@ -127,7 +127,7 @@ Note that only certain style file directives map these constants. DOUBLEQUOTE - " + " COLON @@ -171,7 +171,7 @@ Note that only certain style file directives map these constants. -
+
WHITESPACE The WHITESPACE constant has special properties. When reading data, WHITESPACE refers to sequential runs of SPACES and/or TABS. When @@ -179,50 +179,50 @@ writing data, WHITESPACE is always a single SPACE. For example, the following line: - SOME_NAME 30.1208 -91.1365 SOME OTHER NAME + SOME_NAME 30.1208 -91.1365 SOME OTHER NAME Parses into the following data fields: - SOME_NAME,30.1208,-91.1365,SOME,OTHER,NAME + SOME_NAME,30.1208,-91.1365,SOME,OTHER,NAME
-
+
COMMENTS Anything after a hash (#) on a line is not parsed. For example: - #THIS ENTIRE LINE IS A COMMENT. -#FIELD LAT_DECIMAL, "", "%f" THIS ENTIRE LINE IS A COMMENT -FIELD LAT_DECIMAL, "", "%f" # ONLY THIS SENTENCE IS A COMMENT. + #THIS ENTIRE LINE IS A COMMENT. +#FIELD LAT_DECIMAL, "", "%f" THIS ENTIRE LINE IS A COMMENT +FIELD LAT_DECIMAL, "", "%f" # ONLY THIS SENTENCE IS A COMMENT.
-
+
Global Properties of the File There are a few available directives to describe general traits of the file being described and not specific data within the file itself. -
+
DESCRIPTION This is the description of the file format being described. This text appears in the help screens and in menus used by the various GUI wrappers.
-
+
EXTENSION This directive gives the filename extension generally associated with this file.
-
+
ENCODING Describes the character set used by this format. The value given must be one listed by 'gpsbabel -l'. example: - ENCODING UTF-8 # Use UTF-8 for input and output. + ENCODING UTF-8 # Use UTF-8 for input and output.
-
+
DATUM This value specifies the GPS datum to be used on read or write. Valid values for this option are listed in @@ -234,70 +234,70 @@ option are listed in . - DATUM European 1950 + DATUM European 1950
-
+
DATATYPE Specifies the kind of data we have to read or write. By default all data are seen as waypoint data. With DATATYPE you are now able to bind a specific type to this format. Possible values are WAYPOINT, ROUTE or TRACK. - DATATYPE ROUTE # route-only format + DATATYPE ROUTE # route-only format
-
+
GPSBabel Behavior Directives There are a few available directives to control some of the internal processing functions of GPSBabel. -
+
SHORTLEN This sets the maximum allowed shortname length when using the internal shortname synthesizer. example: - SHORTLEN 16 # shortnames will be at most 16 characters long. + SHORTLEN 16 # shortnames will be at most 16 characters long.
-
+
SHORTWHITE This tells the shortname synthesizer whether or not to allow whitespace in the synthesized shortnames. Allowed values are zero and one. example: - SHORTWHITE 0 # Do not allow whitespace in shortname. + SHORTWHITE 0 # Do not allow whitespace in shortname. SHORTWHITE 1 # Allow whitespace in shortname.
-
+
Defining the Layout of the File The first few directives define the layout the physical file itself: -
+
FIELD_DELIMITER The field delimiter defines the character(s) that separate the fields in the rows of data inside the XCSV file. Common field delimiters are commas - and tabs. (referred to as "comma separated values" and "tab separated - values") + and tabs. (referred to as "comma separated values" and "tab separated + values") examples: - FIELD_DELIMITER COMMA + FIELD_DELIMITER COMMA FIELD_DELIMITER ~ The directive FIELD_DELIMITER is parsed for STYLE CONSTANTS as defined in the table above.
-
+
FIELD_ENCLOSER The field encloser defines the character(s) that surround the field values. Common field enclosers are single and double quote marks. Many styles will @@ -305,14 +305,14 @@ processing functions of GPSBabel. examples: - FIELD_ENCLOSER DOUBLEQUOTE + FIELD_ENCLOSER DOUBLEQUOTE FIELD_ENCLOSER SINGLEQUOTE The directive FIELD_ENCLOSER is parsed for STYLE CONSTANTS as defined in the table above.
-
+
RECORD_DELIMITER The record delimiter defines that character(s) that separate ROWS of data (FIELDS) in the XCSV file. The most common record delimiters @@ -320,14 +320,14 @@ processing functions of GPSBabel. examples: - RECORD_DELIMITER NEWLINE + RECORD_DELIMITER NEWLINE RECORD_DELIMITER | The directive RECORD_DELIMITER is parsed for STYLE CONSTANTS as defined in the table above.
-
+
BADCHARS Bad characters are things that should *never* be written into the XCSV file as data on output. GPSBabel automatically includes any non-blank @@ -336,28 +336,28 @@ processing functions of GPSBabel. examples: - BADCHARS COMMA + BADCHARS COMMA BADCHARS ~| The directive BADCHARS is parsed for STYLE CONSTANTS as defined in the table above.
-
+
PROLOGUE A prologue is basically constant data that is written to the output file BEFORE any waypoints are processed. PROLOGUE can be defined - multiple times in the style file, once for each "line" before the data - begins. This is commonly used in XCSV files as a "header" row. + multiple times in the style file, once for each "line" before the data + begins. This is commonly used in XCSV files as a "header" row. examples: - PROLOGUE OziExplorer Waypoint File Version 1.1 + PROLOGUE OziExplorer Waypoint File Version 1.1 PROLOGUE WGS 84 PROLOGUE Symbol,Name,Latitude,Longitude
-
+
EPILOGUE An Epilogue is the same as a prologue, except this data is written at the END of the file. See the examples for PROLOGUE above. @@ -365,35 +365,35 @@ processing functions of GPSBabel.
-
+
Defining Fields Within the File A field defines data. There are two different classifications of FIELDS, IFIELD (file input) and OFIELD (file output). In the absence of any OFIELDS, IFIELDS are use as both input and output. The existence of OFIELDS is primarily to allow more flexible mapping of GPSBabel data to output data -(say, for instance, to map the internal GPSBabel "description" variable to +(say, for instance, to map the internal GPSBabel "description" variable to two or more fields on output). For all practical purposes, IFIELDS and OFIELDS are defined the same way in the style file. The following per-field options are defined: - "no_delim_before" is supported on in OFIELD tags to specify that this + "no_delim_before" is supported on in OFIELD tags to specify that this field should be written without a field delimiter before it. It's useful for limited field concatenation. - "absolute" is supported on OFIELD tags for lat and lon to indicate + "absolute" is supported on OFIELD tags for lat and lon to indicate that only absolute values (never negative) are to be printed. - "optional" is supported only OFIELD tags and indicates that the + "optional" is supported only OFIELD tags and indicates that the field may or may not be available in the source data. If the field is absent, no trailing field separator is written. - This attribute is most useful when paired with "no_delim_before" as + This attribute is most useful when paired with "no_delim_before" as it allows you to concatenate fields without concern for whether those fields are actually populated or not. @@ -411,7 +411,7 @@ parsed from input and written to output. The fields used by the XCSV parser are as follows: -
+
IGNORE IGNORE fields are, guess what, ignored on input. Internally, IGNORE fields are treated as CHARACTER data, and as such, require a printf @@ -419,11 +419,11 @@ parsed from input and written to output. examples: - IFIELD IGNORE,"","%14.14s" # (writes a 14 character blank field) - IFIELD IGNORE,"","%s" # (writes a blank field on output) + IFIELD IGNORE,"","%14.14s" # (writes a 14 character blank field) + IFIELD IGNORE,"","%s" # (writes a blank field on output)
-
+
CONSTANT CONSTANT fields are, of course, constant. They are ignored on input, however they write CONSTANT data on output. As such, they require a @@ -431,11 +431,11 @@ parsed from input and written to output. examples: - IFIELD CONSTANT,"FFFFFF","%s" # (writes "FFFFFF" in the field) - IFIELD CONSTANT,"01/01/70","%s" # (a constant date field) + IFIELD CONSTANT,"FFFFFF","%s" # (writes "FFFFFF" in the field) + IFIELD CONSTANT,"01/01/70","%s" # (a constant date field)
-
+
INDEX An INDEX field is used ONLY on output. The INDEX constant defines a field that, at output, contains the sequence number of the waypoint being @@ -446,12 +446,12 @@ parsed from input and written to output. examples: - IFIELD INDEX,"0","%04d" # (Starts counting at zero) - IFIELD INDEX,"","%04d" # (Starts counting at zero) - IFIELD INDEX,"1","%04d" # (Starts counting at one) + IFIELD INDEX,"0","%04d" # (Starts counting at zero) + IFIELD INDEX,"","%04d" # (Starts counting at zero) + IFIELD INDEX,"1","%04d" # (Starts counting at one)
-
+
SHORTNAME A SHORTNAME is generally the waypoint name of the data being processed. SHORTNAME maps directly to the GPSBabel variable ->shortname. A SHORTNAME @@ -459,10 +459,10 @@ parsed from input and written to output. example: - IFIELD SHORTNAME,"","%s" + IFIELD SHORTNAME,"","%s"
-
+
DESCRIPTION A DESCRIPTION is generally a long description of the waypoint. A DESCRIPTION maps to the GPSBabel variable ->description and is otherwise @@ -470,27 +470,27 @@ parsed from input and written to output. examples: - IFIELD DESCRIPTION,"","%s" + IFIELD DESCRIPTION,"","%s"
-
+
NOTES NOTES are generally everything else about a waypoints. NOTES map to the GPSBabel variable ->notes and is otherwise handled exactly like a SHORTNAME.
-
+
URL URL is a URL for the waypoint. URL maps to the GPSBabel variable ->url and is otherwise handled exactly like a SHORTNAME. example: - IFIELD URL,"","%s" + IFIELD URL,"","%s"
-
+
URL_LINK_TEXT URL_LINK_TEXT is a textual description of where a URL points. URL_LINK_TEXT maps to the GPSBabel variable ->url_link_text and @@ -498,10 +498,10 @@ parsed from input and written to output. example: - IFIELD URL_LINK_TEXT,"","%s" + IFIELD URL_LINK_TEXT,"","%s"
-
+
ICON_DESCR ICON_DESCR is a textual description of an icon type for a waypoint. ICON_DESCR maps to the GPSBabel variable ->icon_desc and is otherwise @@ -509,10 +509,10 @@ parsed from input and written to output. example: - IFIELD ICON_DESCR,"","%s" + IFIELD ICON_DESCR,"","%s"
-
+
LAT_DECIMAL LAT_DECIMAL defines LATITUDE in DECIMAL format. Note that this is a PURE signed decimal format (i.e. -91.0000). This data is handled internally as @@ -520,15 +520,15 @@ parsed from input and written to output. example: - IFIELD LAT_DECIMAL,"","%f" + IFIELD LAT_DECIMAL,"","%f"
-
+
LON_DECIMAL See LAT_DECIMAL, except LON_DECIMAL defines LONGITUDE.
-
+
LAT_INT32DEG LAT_INT32DEG defines LATITUDE in what I call INT32DEGREES. This value is a signed LONG INTEGER and requires a LONG INTEGER printf conversion. @@ -536,15 +536,15 @@ parsed from input and written to output. example: - IFIELD LAT_INT32DEG,"","%ld" + IFIELD LAT_INT32DEG,"","%ld"
-
+
LON_INT32DEG See LON_INT32DEG except LON_INT32DEG defines LONGITUDE.
-
+
LAT_DECIMALDIR / LAT_DIRDECIMAL LAT_DECIMALDIR and LAT_DIRDECIMAL define LATITUDE in DECIMAL format with the added bonus of a 'N/S' or 'E/W' direction character. This data @@ -556,23 +556,23 @@ parsed from input and written to output. examples: - IFIELD LAT_DECIMALDIR,"","%f %c" # (writes 31.333 N) - IFIELD LAT_DIRDECIMAL,"","%c %f" # (writes N 31.333) + IFIELD LAT_DECIMALDIR,"","%f %c" # (writes 31.333 N) + IFIELD LAT_DIRDECIMAL,"","%c %f" # (writes N 31.333)
-
+
LON_DECIMALDIR / LON_DIRDECIMAL Same as LAT_DECIMALDIR / LAT_DIRDECIMAL except LON_ defines LONGITUDE.
-
+
LAT_DIR / LON_DIR LAT_DIR returns the single character 'N' or 'S' depending on the hemisphere of the latitude. LON_DIR returns 'E' or 'W' depending on the hemisphere of the longitude.
-
+
LAT_HUMAN_READABLE LAT_HUMAN_READABLE defines LATITUDE in a human-readable format. This format is probably the most expressive format. It is similar to @@ -583,17 +583,17 @@ parsed from input and written to output. examples: - # (writes N 31 40.000) - IFIELD LAT_HUMAN_READABLE,"","%c %d %f" - # (writes "31 deg 40.000 min N") - IFIELD LAT_HUMAN_READABLE,"","%d deg %f min %c" + # (writes N 31 40.000) + IFIELD LAT_HUMAN_READABLE,"","%c %d %f" + # (writes "31 deg 40.000 min N") + IFIELD LAT_HUMAN_READABLE,"","%d deg %f min %c" # Note that this string will confuse the reading routine due - # to the letter "n" in "min" and the letter "e" in "deg." + # to the letter "n" in "min" and the letter "e" in "deg." # (writes 31 40 00.000N) - IFIELD LAT_HUMAN_READABLE,"","%d %d %f%c" + IFIELD LAT_HUMAN_READABLE,"","%d %d %f%c"
-
+
MAP_EN_BNG MAP_EN_BNG converts coordinates from/to British National Grid (BNG). @@ -602,16 +602,16 @@ parsed from input and written to output. examples: - IFIELD MAP_EN_BNG,"","%s%5d %5d" # (writes i.e. "SJ00001 00001") - IFIELD MAP_EN_BNG,"","%s %d %d" # (writes i.e. "TQ 888 999") + IFIELD MAP_EN_BNG,"","%s%5d %5d" # (writes i.e. "SJ00001 00001") + IFIELD MAP_EN_BNG,"","%s %d %d" # (writes i.e. "TQ 888 999")
-
+
LON_HUMAN_READABLE See LAT_HUMAN_READABLE except LON_HUMAN_READABLE defines LONGITUDE.
-
+
LATLON_HUMAN_READABLE LATLON_HUMAN_READABLE is like LAT_HUMAN_READABLE and LON_HUMAN_READABLE except that it reads and writes both latitude and longitude as a single @@ -621,53 +621,53 @@ parsed from input and written to output. example: - IFIELD LATLON_HUMAN_READABLE,"","%c %d %f" - # (writes "N 31 40.126 W 85 09.62" as a single field) + IFIELD LATLON_HUMAN_READABLE,"","%c %d %f" + # (writes "N 31 40.126 W 85 09.62" as a single field)
-
+
LAT_NMEA Defines the latitude in the format used by the NMEA standard which is degrees multiplied by 100 plus decimal minutes. example: - IFIELD LAT_NMEA, "%f", "%08.3f" # (writes 3558.322) + IFIELD LAT_NMEA, "%f", "%08.3f" # (writes 3558.322)
-
+
LAT_DDMMDIR Derived from the LAT_NMEA latitude format, with degrees * 100 plus decimal minutes, but using an additional specifier to position the 'N' or 'S' instead of a leading minus sign (or absence thereof) to give direction from zero. - IFIELD LAT_DDMMDIR, "%f", "%08.3f%c" # (writes "5334.192S" giving -53.56987 degrees latitude) + IFIELD LAT_DDMMDIR, "%f", "%08.3f%c" # (writes "5334.192S" giving -53.56987 degrees latitude)
-
+
LON_NMEA Defines the longitude in the format used by the NMEA standard which is degrees multiplied by 100 plus decimal minutes. Example: - IFIELD LON_NMEA, "%f", "%010.3f" # (writes -08708.082) + IFIELD LON_NMEA, "%f", "%010.3f" # (writes -08708.082)
-
+
LON_DDMMDIR Derived from the LON_NMEA longitude format, with degrees * 100 plus decimal minutes, but using an additional character format character to position the 'E' or 'W' instead of a leading minus sign (or absence thereof) to give direction from zero. Example: - IFIELD LON_DDMMDIR, "%f", "%010.3f%c" # (writes "01232.745W" giving -12.54575 degrees + IFIELD LON_DDMMDIR, "%f", "%010.3f%c" # (writes "01232.745W" giving -12.54575 degrees longitude)
-
+
LAT_10EX / LON_10EX Defines the latitude or longitude in the format used i.e. by TomTom Navigator itinerary files. It is degrees multiplied by 10 power X. X have to be replaced with @@ -676,59 +676,59 @@ longitude) examples: - IFIELD LAT_10E5, "%f", "%.f" # (writes 3558322) + IFIELD LAT_10E5, "%f", "%.f" # (writes 3558322) - IFIELD LON_10E5, "%f", "%.f" # (writes -8708082) + IFIELD LON_10E5, "%f", "%.f" # (writes -8708082)
-
+
UTM A location in UTM has several components: a zone, a northing, and an easting. The UTM format specifier is the most common representation of these. example: - IFIELD UTM, "", "%s" # writes 6S 519045 3984035 -the easting is first by convention. + IFIELD UTM, "", "%s" # writes 6S 519045 3984035 -the easting is first by convention.
-
+
UTM_EASTING This is the decimal component representing the easting example: - IFIELD UTM_EASTING, "", "%.0f" # outputs 519045 + IFIELD UTM_EASTING, "", "%.0f" # outputs 519045
-
+
UTM_NORTHING This is the decimal component representing the northing example: - IFIELD UTM_NORTHING "", "%.0f" # outputs 3984035 + IFIELD UTM_NORTHING "", "%.0f" # outputs 3984035
-
+
UTM_ZONE The UTM zone. example: - IFIELD UTM_ZONE "", "%d" # outputs 6 + IFIELD UTM_ZONE "", "%d" # outputs 6
-
+
UTM_ZONEC The UTM Zone character. example: - IFIELD UTM_ZONEC "", "%c" # outputs S + IFIELD UTM_ZONEC "", "%c" # outputs S
-
+
<para>The full UTM zone and latitude band. </para> <para>example: </para> - <screen format="linespecific">IFIELD UTM_ZONEF "", "%d%c" # outputs 6S + <screen>IFIELD UTM_ZONEF "", "%d%c" # outputs 6S </screen> </section> - <section id="style_def_altfeet"> + <section xml:id="style_def_altfeet"> <title>ALT_FEET ALT_FEET is the position's ALTITUDE in FEET. This value is treated as a SIGNED DOUBLE PRECISION FLOAT and requires a FLOATING POINT printf @@ -736,64 +736,64 @@ longitude) example: - IFIELD ALT_FEET,"","%.0f" + IFIELD ALT_FEET,"","%.0f"
-
+
ALT_METERS ALT_METERS is identical to ALT_FEET with the exception that the altitude is in METERS.
-
+
HEART_RATE Heart rate, measured in beats per minute. Only valid for units with heart rate monitor features (i.e. Garmin Forerunner 301). example: - IFIELD HEART_RATE,"","%d" + IFIELD HEART_RATE,"","%d"
-
+
CADENCE Cadence in revolutions per minute. Only valid for units with heart rate monitor features (i.e. Garmin Edge 305). example: - IFIELD CADENCE,"","%d" + IFIELD CADENCE,"","%d"
-
+
POWER Cycling power in Watts. Only valid for units with power meter features (i.e. Garmin Edge 305). example: - IFIELD POWER,"","%.1f" + IFIELD POWER,"","%.1f"
-
+
TEMPERATURE Temperature in degrees Celsius. example: - IFIELD TEMPERATURE,"","%.1f" + IFIELD TEMPERATURE,"","%.1f"
-
+
TEMPERATURE_F Temperature in degrees Fahrenheit. example: - IFIELD TEMPERATURE_F,"","%.1f" + IFIELD TEMPERATURE_F,"","%.1f"
-
+
EXCEL_TIME EXCEL_TIME is the waypoint's creation time, if any. This is actually the decimal days since 1/1/1900 and is handled internally as a DOUBLE @@ -801,10 +801,10 @@ longitude) example: - IFIELD EXCEL_TIME,"","%11.5f" + IFIELD EXCEL_TIME,"","%11.5f"
-
+
TIMET_TIME TIMET_TIME is the waypoint's creation time, if any. This is actually the integer seconds since 1970-01-01T00:00:00 UTC. It @@ -813,10 +813,10 @@ longitude) example: - IFIELD TIMET_TIME,"","%lld" + IFIELD TIMET_TIME,"","%lld"
-
+
TIMET_TIME_MS TIMET_TIME_MS is the same as TIMET_TIME, but expressed in milliseconds. It too is handled internally as a 64 bit integer and requires a LONG LONG INTEGER @@ -824,10 +824,10 @@ longitude) example: - IFIELD TIMET_TIME_MS,"","%lld" + IFIELD TIMET_TIME_MS,"","%lld"
-
+
YYYYMMDD_TIME YYYYMMDD_TIME is the waypoint's creation time, if any. It's a single decimal field containing four digits of year, two digits of month, @@ -836,17 +836,17 @@ longitude) example: - IFIELD YYYYMMDD_TIME,"","%ld" + IFIELD YYYYMMDD_TIME,"","%ld"
-
+
GMT_TIME GMT_TIME is the waypoint's creation time, in UTC time zone. It uses the strptime conversion format tags. example: - IFIELD GMT_TIME,"","%m/%d/%Y %I:%M:%D %p" + IFIELD GMT_TIME,"","%m/%d/%Y %I:%M:%D %p" Search the web for 'strptime man page' for details strptime, but one such page can be found at @@ -857,9 +857,9 @@ longitude) - http://www.die.net/doc/linux/man/man3/strptime.3.html + http://www.die.net/doc/linux/man/man3/strptime.3.html
-
+
LOCAL_TIME LOCAL_TIME is the waypoint's creation time, in the local time zone. It uses strptime conversion format tags. See GMT_TIME for a @@ -867,10 +867,10 @@ longitude) example: - IFIELD LOCAL_TIME,"","%y-%m-%d" + IFIELD LOCAL_TIME,"","%y-%m-%d"
-
+
HMSG_TIME HMSG_TIME parses up to three time parts and am/pm string to add this value to the previously parsed *_TIME field that contains @@ -878,10 +878,10 @@ longitude) example: - IFIELD HMSG_TIME,"","%d:%d:%d %s" + IFIELD HMSG_TIME,"","%d:%d:%d %s"
-
+
HMSL_TIME HMSG_TIME parses up to three time parts and am/pm string to add this value to the previously parsed *_TIME field that contains @@ -889,10 +889,10 @@ longitude) example: - IFIELD HMSL_TIME,"","%dh%dm" + IFIELD HMSL_TIME,"","%dh%dm"
-
+
ISO_TIME ISO_TIME is the waypoint's creation time, in ISO 8601 format, which include time zone information. @@ -903,10 +903,10 @@ longitude) example: - IFIELD ISO_TIME,"","%s" + IFIELD ISO_TIME,"","%s"
-
+
ISO_TIME_MS ISO_TIME_MS is much like ISO_TIME, but expresses milliseconds at the end of the timestamp. @@ -917,10 +917,10 @@ longitude) example: - IFIELD ISO_TIME_MS,"","%s" + IFIELD ISO_TIME_MS,"","%s"
-
+
NET_TIME Microsoft dot net represents times in 100 nanosecond intervals since midnight Jan 1/0001 GMT, giving absurdly large numbers like 633943150010000000 for @@ -928,104 +928,104 @@ longitude) example: - IFIELD NET_TIME,"","%lld" + IFIELD NET_TIME,"","%lld"
-
+
GEOCACHE_DIFF GEOCACHE_DIFF is valid only for geocaches and represents a DOUBLE - PRECISION FLOAT. This is the geocache "difficulty" rating as defined by - Groundspeak. A "three and a half star" cache would therefore be "3.5" + PRECISION FLOAT. This is the geocache "difficulty" rating as defined by + Groundspeak. A "three and a half star" cache would therefore be "3.5" example: - IFIELD GEOCACHE_DIFF,"","%3.1f" + IFIELD GEOCACHE_DIFF,"","%3.1f"
-
+
GEOCACHE_TERR GEOCACHE_TERR is valid only for geocaches and represents a DOUBLE - PRECISION FLOAT. This is the geocache "terrain" rating as defined - by Groundspeak. A "three and a half star" cache would therefore be "3.5" + PRECISION FLOAT. This is the geocache "terrain" rating as defined + by Groundspeak. A "three and a half star" cache would therefore be "3.5" example: - IFIELD GEOCACHE_TERR,"","%3.1f" + IFIELD GEOCACHE_TERR,"","%3.1f"
-
+
GEOCACHE_CONTAINER GEOCACHE_CONTAINER is valid only for geocaches and is heavily influenced - by the Groundspeak container types. Examples would include "Micro" - and "Virtual". + by the Groundspeak container types. Examples would include "Micro" + and "Virtual". example: - GEOCACHE_CONTAINER,"","%s" + GEOCACHE_CONTAINER,"","%s"
-
+
GEOCACHE_TYPE GEOCACHE_TYPE is valid only for geocaches and is heavily influenced - by the Groundspeak cache types. Examples would include "Event cache" - and "Multi-Cache". + by the Groundspeak cache types. Examples would include "Event cache" + and "Multi-Cache". example: - GEOCACHE_TYPE,"","%s" + GEOCACHE_TYPE,"","%s"
-
+
GEOCACHE_PLACER GEOCACHE_PLACER is a string containing the name of the placer of a geocache. example: - GEOCACHE_PLACER,"","%s" + GEOCACHE_PLACER,"","%s"
-
+
GEOCACHE_ISAVAILABLE - GEOCACHE_ISAVAILABLE is a string containing "True" or "False" + GEOCACHE_ISAVAILABLE is a string containing "True" or "False" indicating whether a geocache is currently available or not. example: - GEOCACHE_ISAVAILABLE,"","%s" + GEOCACHE_ISAVAILABLE,"","%s"
-
+
GEOCACHE_ISARCHIVED - GEOCACHE_ISARCHIVED is a string containing "True" or "False" + GEOCACHE_ISARCHIVED is a string containing "True" or "False" indicating whether a geocache has been archived. example: - GEOCACHE_ISARCHIVED,"","%s" + GEOCACHE_ISARCHIVED,"","%s"
-
+
GEOCACHE_LAST_FOUND A long integer in format YYYYMMDD containing the last time this geocache was found. example: - GEOCACHE_LAST_FOUND,"","%ld" + GEOCACHE_LAST_FOUND,"","%ld"
-
+
GEOCACHE_HINT The hint for this geocache. No additional transformation (such as rot13) will be performed on this string. example: - GEOCACHE_HINT,"","%s" + GEOCACHE_HINT,"","%s"
-
+
PATH_DISTANCE_MILES PATH_DISTANCE_MILES outputs the total length of the route or track from the start point to the current point, in miles. This and the altitude @@ -1039,28 +1039,28 @@ longitude) example: - PATH_DISTANCE_MILES,"","%f" + PATH_DISTANCE_MILES,"","%f"
-
+
PATH_DISTANCE_NAUTICAL_MILES PATH_DISTANCE_NAUTICAL_MILES is like PATH_DISTANCE_MILES except it outputs the length in nautical miles.
-
+
PATH_DISTANCE_KM PATH_DISTANCE_KM is like PATH_DISTANCE_MILES except it outputs the length in kilometers.
-
+
PATH_DISTANCE_METERS PATH_DISTANCE_METERS is like PATH_DISTANCE_MILES except it outputs the length in meters.
-
+
PATH_SPEED Speed in meters per second. GPSBabel does NOT calculate this data by default; it is read from the input file if present. (If not present, @@ -1075,37 +1075,37 @@ longitude) filter.) example: - PATH_SPEED,"","%f" + PATH_SPEED,"","%f"
-
+
PATH_SPEED_KPH Like PATH_SPEED but means kilometers per hour. example: - PATH_SPEED_KPH,"","%.1f" + PATH_SPEED_KPH,"","%.1f"
-
+
PATH_SPEED_MPH Like PATH_SPEED but means miles per hour. example: - PATH_SPEED_MPH,"","%.1f" + PATH_SPEED_MPH,"","%.1f"
-
+
PATH_SPEED_KNOTS Like PATH_SPEED but means knots (nautical). example: - PATH_SPEED_KNOTS,"","%.1f" + PATH_SPEED_KNOTS,"","%.1f"
-
+
PATH_COURSE Course in degrees. GPSBabel does not calculate this data by default; it is read from the input file if present. (If not present, it may be @@ -1120,30 +1120,30 @@ longitude) filter.) example: - PATH_COURSE,"","%f" + PATH_COURSE,"","%f"
-
+
GPS_HDOP / GPS_VDOP / GPS_PDOP GPS horizontal / vertical / positional dilution of precision parameters. Needs float conversion. example: - GPS_HDOP,"","%f" + GPS_HDOP,"","%f"
-
+
GPS_SAT Number of satellites used for determination of the position. Needs integer conversion. example: - GPS_SAT,"","%d" + GPS_SAT,"","%d"
-
+
GPS_FIX Type of fix (see GPX spec or @@ -1156,10 +1156,10 @@ longitude) filter). Needs string conversion. example: - GPS_FIX,"","%s" + GPS_FIX,"","%s"
-
+
TRACK_NEW If '1', it indicates that this trackpoint is the first point of a new track. Needs integer conversion. example: @@ -1169,9 +1169,9 @@ longitude) - IFIELD TRACK_NEW,"","%d" + IFIELD TRACK_NEW,"","%d"
-
+
TRACK_NAME The name of the track currently being operated on. Needs string conversion. example: @@ -1181,28 +1181,28 @@ longitude) - TRACK_NAME, "", "%s" + TRACK_NAME, "", "%s"
-
+
ROUTE_NAME The name of the route currently being operated on. Needs string conversion. example: - ROUTE_NAME, "", "%s" + ROUTE_NAME, "", "%s"
-
+
STREET_ADDR Street address including house number. Notice that this is not used for any geocoding, it's merely textual description associated with a position. example: - STREET_ADDR, "", "%s" + STREET_ADDR, "", "%s"
-
+
CITY - The name of a city. Sometimes part of "Points of Interest". This is simple textual data associated with a position, no geocoding will be done.. + The name of a city. Sometimes part of "Points of Interest". This is simple textual data associated with a position, no geocoding will be done.. example: - CITY, "", "%s" + CITY, "", "%s"
-
+
COUNTRY The name of a country associated with a position. example: @@ -1212,9 +1212,9 @@ longitude) - COUNTRY, "", "%s" + COUNTRY, "", "%s"
-
+
EMAIL An email address associated with a position. example: @@ -1224,9 +1224,9 @@ longitude) - EMAIL, "", "%s" + EMAIL, "", "%s"
-
+
FACILITY The name of a facility to associate with a position. example: @@ -1236,9 +1236,9 @@ longitude) - FACILITY, "", "%s" + FACILITY, "", "%s"
-
+
PHONE_NR A phone number associated with a position. This is just textual data attached for convenience. example: @@ -1248,9 +1248,9 @@ longitude) - PHONE_NR, "", "%s" + PHONE_NR, "", "%s"
-
+
POSTAL_CODE A postal code to associate with a position. It is freeform text and is not used by GPSBabel for any geocoding or such. example: @@ -1260,9 +1260,9 @@ longitude) - POSTAL_CODE, "", "%s" + POSTAL_CODE, "", "%s"
-
+
FILENAME The name of the input file from where the points were loaded. This field is available only on output. example: @@ -1272,9 +1272,9 @@ longitude) - OFIELD FILENAME, "", "%s" + OFIELD FILENAME, "", "%s"
-
+
FORMAT The name of the input format from where format the points came. This field is available only on output. example: @@ -1284,11 +1284,11 @@ longitude) - OFIELD FORMAT, "", "%s" + OFIELD FORMAT, "", "%s"
-
+
Examples Here is one example style file from the GPSBabel source. @@ -1318,19 +1318,19 @@ SHORTLEN 24 # # INDIVIDUAL DATA FIELDS, IN ORDER OF APPEARANCE: # -IFIELD LON_HUMAN_READABLE, "", "%08.5f" -IFIELD LAT_HUMAN_READABLE, "", "%08.5f" -IFIELD SHORTNAME, "", "%s" -IFIELD DESCRIPTION, "", "%s" - -OFIELD LON_DECIMAL, "", "%08.5f" -OFIELD LAT_DECIMAL, "", "%08.5f" -OFIELD SHORTNAME, "", "%-.24s" -OFIELD GEOCACHE_TYPE, "", " %-.4s", "no_delim_before,optional" -OFIELD GEOCACHE_CONTAINER, "", "/%-.4s ", "no_delim_before,optional" -OFIELD GEOCACHE_DIFF, "", "(%3.1f", "no_delim_before,optional" -OFIELD GEOCACHE_TERR, "", "/%3.1f)", "no_delim_before,optional" -OFIELD DESCRIPTION, "", "%-.50s" +IFIELD LON_HUMAN_READABLE, "", "%08.5f" +IFIELD LAT_HUMAN_READABLE, "", "%08.5f" +IFIELD SHORTNAME, "", "%s" +IFIELD DESCRIPTION, "", "%s" + +OFIELD LON_DECIMAL, "", "%08.5f" +OFIELD LAT_DECIMAL, "", "%08.5f" +OFIELD SHORTNAME, "", "%-.24s" +OFIELD GEOCACHE_TYPE, "", " %-.4s", "no_delim_before,optional" +OFIELD GEOCACHE_CONTAINER, "", "/%-.4s ", "no_delim_before,optional" +OFIELD GEOCACHE_DIFF, "", "(%3.1f", "no_delim_before,optional" +OFIELD GEOCACHE_TERR, "", "/%3.1f)", "no_delim_before,optional" +OFIELD DESCRIPTION, "", "%-.50s" When used on a Groundspeak Pocket Query, it will output lines that look like: @@ -1352,13 +1352,13 @@ look like: subdirectory of the GPSBabel source tree or at the - online source. + online source. .
-
+
Miscellaneous Notes -
+
Default Values Default values are supported for any output fields that contain pure character data output such as URL and NOTES. Default values are only @@ -1370,4 +1370,3 @@ look like:
- diff --git a/xmldoc/chapters/use.xml b/xmldoc/chapters/use.xml index 555ed8638..ce7bec3e8 100644 --- a/xmldoc/chapters/use.xml +++ b/xmldoc/chapters/use.xml @@ -1,6 +1,6 @@ - + Usage - +
Invocation If you're using GPSBabel, you will need to know how to do at least two things: read data from a file, and write it to another file. There are four basic @@ -92,29 +92,29 @@ name of a file to be read or written. This command will read from a Magellan unit attached to the first serial port on a Linux system (device names will vary on other OSes; typically COMx: on Windows) and write them as a geocaching loc file. - + Command showing Linux download from Magellan serial and writing to .loc file gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc This second command does the same on Microsoft Windows. - + Command showing Windows download from Magellan serial and writing to .loc file gpsbabel -i magellan -f com1 -o geo -F mag.loc Optionally, you may specify - -s + -s in any command line. This - causes the program to ignore any "short" names that may be + causes the program to ignore any "short" names that may be present in the source data format and synthesize one from the long name. This is particularly useful if you're writing to a target format that isn't the lowest common denominator but the source data was written for the lowest common denominator. This is useful for writing data from geocaching.com - to a GPS so my waypoints have "real" names instead of + to a GPS so my waypoints have "real" names instead of the 'GC1234' ones that are optimized for receivers of the lowest common denominator. A geocacher using Linux with a Magellan receiver may thus find commands @@ -126,8 +126,8 @@ name of a file to be read or written. gpsbabel -s -i geo -f geocaching.loc -o magellan -F com1 - - +
+
Suboptions Many of the available format options in GPSBabel can themselves take options. While we try to make all the formats do the most @@ -140,7 +140,7 @@ name of a file to be read or written. : - gpsbabel -i gpx -f file.gpx -o kml,deficon="file://myicon.png",lines=0 -F one.kml -o kml -F two.kml + gpsbabel -i gpx -f file.gpx -o kml,deficon="file://myicon.png",lines=0 -F one.kml -o kml -F two.kml This command will read the GPX file file.gpx @@ -158,8 +158,8 @@ name of a file to be read or written. filetype are documented on the page in this document that describes the option itself. - - +
+
Advanced Usage Argument are processed in the order they appear on the command line and are translated internally into a pipeline that data flows @@ -176,32 +176,32 @@ merged data to multiple destinations. The input file type remains unchanged until a new - -i + -i argument is seen. Files are read in the order they appear. So you could merge three input files into one output file with: - + Merging multiple files into one gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc You can merge files of different types: - + Merging multiple files of differing types. gpsbabel -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx -o gpsutil -F big.gps - + Writing the same data in multiple output formats. You can write the same data in different output formats: gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx -F 1.wpt - - +
+
Route and Track Modes Most formats supported by GPSBabel will make a reasonable attempt to work transparently with waypoints, tracks, and routes. Some @@ -210,13 +210,13 @@ merged data to multiple destinations. and magellan require the - -t + -t flag to work with tracks and - -r + -r to work with routes. - -w + -w is for waypoints, and is the default. So if you wanted to read all data from a Magellan Meridian GPS receiver into a gpx file, you might use a command @@ -243,17 +243,17 @@ merged data to multiple destinations. always result in a list of waypoints, not the original track. The presence of - -s + -s on the command line tends to create havoc on tracks and routes since many of these formats rely on internal linkages between such points and renaming them may break those linkages. In general, don't use - -s + -s when tracks or routes are present. - - +
+
Working with predefined options GPSBabel can read a file on startup to set defaults for options. All module and filter options may be set this way. @@ -315,7 +315,7 @@ merged data to multiple destinations. current working directory - Windows: all paths "APPDATA", "WINDIR", "SYSTEMROOT" declared in environment. + Windows: all paths "APPDATA", "WINDIR", "SYSTEMROOT" declared in environment. Unix like OS'ses: @@ -335,10 +335,10 @@ merged data to multiple destinations. The inifile mechanism can be disabled with an empty filename. - gpsbabel -p "" -i gpx -f something.gpx -o tiger -F - + gpsbabel -p "" -i gpx -f something.gpx -o tiger -F - - - +
+
Realtime tracking Introduced in GPSBabel 1.3.1, we now have an experimental @@ -355,7 +355,7 @@ merged data to multiple destinations. inputs. KML, NMEA, and the various XCSV formats are supported on output. Additional formats may be added by interested parties later. - + Read realtime positioning from Garmin USB, write to Keyhole Markup gpsbabel -T -i garmin -f usb: -o kml -F example.kml @@ -364,7 +364,7 @@ merged data to multiple destinations. suitable for a self-refreshing network link in Google Earth. - + Read realtime positioning from Wintec WBT-201 via Bluetooth on Mac, write to Keyhole Markup gpsbabel -T -i nmea -f /dev/cu.G-Rays2-SPPslave-1 -o kml -F example.kml @@ -389,10 +389,10 @@ merged data to multiple destinations. Garmin USB . These names - (except the "usb:" parlance for Garmin USB) are assigned by + (except the "usb:" parlance for Garmin USB) are assigned by your operating system. - - +
+
Batch mode (command files) In addition to reading arguments from the command line, GPSBabel can read directions from batch (or command) files via the @@ -417,10 +417,10 @@ merged data to multiple destinations. -i gdb -f croatia_2006.gdb -x nuketypes,waypoints,routes - -x track,pack,split,title="LOG # %Y%m%d" + -x track,pack,split,title="LOG # %Y%m%d" - - +
+
List of Options The complete list of available options to GPSBabel can be obtained by running @@ -434,9 +434,9 @@ merged data to multiple destinations. for more info. - Write "smart" names. This option influences some - but not all - of our writers to try to build "smart" waypoint names. For example, in modules that know about geocaching, it may replace "GC1234" with the actual name of the geocache. + Write "smart" names. This option influences some - but not all - of our writers to try to build "smart" waypoint names. For example, in modules that know about geocaching, it may replace "GC1234" with the actual name of the geocache. - Work on routes. This option has a subtly different meaning in different cases. As the very first formats in GPSBabel were for serial GPSes and routes and tracks were large and thus time-consuming to transfer, the default was waypoints only with this option to turn on the extra data. Some of our file formats use this option to mean "work only on routes, even if you have tracks/waypoints", but we're trying to discourage that behavior and in most cases, consider it a bug. + Work on routes. This option has a subtly different meaning in different cases. As the very first formats in GPSBabel were for serial GPSes and routes and tracks were large and thus time-consuming to transfer, the default was waypoints only with this option to turn on the extra data. Some of our file formats use this option to mean "work only on routes, even if you have tracks/waypoints", but we're trying to discourage that behavior and in most cases, consider it a bug. Work on tracks. See @@ -458,5 +458,5 @@ merged data to multiple destinations. Print help. Print version number. - +
diff --git a/xmldoc/convertdoc b/xmldoc/convertdoc new file mode 100755 index 000000000..047e4250c --- /dev/null +++ b/xmldoc/convertdoc @@ -0,0 +1,76 @@ +#!/bin/bash -e + +fixem() { +encapsulate=$1 +echo encapsulate "$encapsulate" +for file in *.xml +do +if [ "$file" != "allchapters.xml" ]; then +if [ "$file" != "_chapters.xml" ]; then + echo "converting $file ($(wc -c "$file" | awk '{print $1}') bytes)" + if [ "$encapsulate" = "yes" ]; then + echo -e "\n\nT\n$(cat $file)" > "$file" + echo "" >> "$file" + fi + xmllint --noout --valid "$file" || true + # db4-upgrade.xsl from https://docbook.org/xml/5.1/docbook-v5.1-os.zip + xsltproc -o "$file".new /home/tsteven4/builds/docbook-v5.1/tools/db4-upgrade.xsl "$file" + if [ "$encapsulate" == "yes" ]; then + head --lines=-1 "$file".new | tail --lines=+3 > "$file" + else + tail --lines=+2 "$file".new > "$file" + fi + rm "$file".new +fi +fi +done +} + +pushd xmldoc +pushd formats +fixem yes +# 4.5 productname defaulted to class=trade. 5.0 does not, use trademark +for file in *.xml +do + echo -e "\n$(cat $file)" > "$file" + echo "" >> "$file" + xsltproc -o "$file".trademark ../tmissue.xsl "$file" + head --lines=-1 "$file".trademark | tail --lines=+2 > "$file" + rm "$file".trademark +done +pushd options +# for some reason the upgrade wants to insert a ^L character in gpx-urlbase.xml unless we +sed -e 's|\\|\\\\|g' -i gpx-urlbase.xml +sed -e 's|\\|\\\\|g' -i subrip-format.xml +sed -e 's|\\|\\\\|g' -i exif-filename.xml +fixem yes +popd +popd +pushd filters +fixem yes +pushd options +fixem yes +popd +popd +pushd chapters +sed -e 's|&filters;|[[[filters]]]|' -i filters.xml +sed -e 's|&formats;|[[[formats]]]|' -i formats.xml +fixem no +sed -e 's|\[\[\[filters\]\]\]|\&filters;|' -i filters.xml +sed -e 's|\[\[\[formats\]\]\]|\&formats;|' -i formats.xml +#sed -i -e '$a\' formats.xml +#sed -i -e '$a\' filters.xml +popd +# the 5.1 version of db4-update.xsl drops the term/ulink +patch -p0 - + # Lima Road/SR3 north of Fort Wayne, Indiana 41.150064468 -85.166207433 41.150064468 -85.165371895 @@ -30,14 +30,13 @@ such a gap by inserting a line containing "#break" either on a line by itself or after the coordinates of the starting point of the new arc segment. - + Using the arc filter Assuming the arc above is in a file called -lima_rd.txt, the following command line +lima_rd.txt, the following command line would include only points within one mile of the section of Lima Road covered by the arc. gpsbabel -i geo -f 1.loc -x arc,file=lima_rd.txt,distance=1 -o mapsend -F 2.wpt - diff --git a/xmldoc/filters/bend.xml b/xmldoc/filters/bend.xml index 677ee2cd8..a6a69e616 100644 --- a/xmldoc/filters/bend.xml +++ b/xmldoc/filters/bend.xml @@ -29,4 +29,3 @@ larger than 5 degrees. gpsbabel -i gpx -f route.gpx -x bend,distance=25,interpolate,minangle=5 -o gpx -F newroute.gpx - diff --git a/xmldoc/filters/discard.xml b/xmldoc/filters/discard.xml index e3804ea65..8e224b3ff 100644 --- a/xmldoc/filters/discard.xml +++ b/xmldoc/filters/discard.xml @@ -8,7 +8,7 @@ that must have been in view for a fix to be considered, or both. HDOP and VDOP are measures of the best possible horizontal or vertical precision for a given configuration of GPS satellites. Higher numbers indicate a higher dilution of precision and therefore mathematically less useful. - + Using the discard filter for HDOP and VDOP. gpsbabel -i gpx -f in.gpx -x discard,hdop=10,vdop=20,hdopandvdop -o gpx -F out.gpx @@ -17,10 +17,9 @@ HDOP and VDOP are measures of the best possible horizontal or vertical precision You may specify a minimum number of satellites. - + Using the discard filter to require at least three satellites. gpsbabel -i gpx -f in.gpx -x discard,sat=3 -o gpx -F out.gpx Contributed by Tobias Minich and Serge Droz. - diff --git a/xmldoc/filters/duplicate.xml b/xmldoc/filters/duplicate.xml index 46a8f09f5..922522f49 100644 --- a/xmldoc/filters/duplicate.xml +++ b/xmldoc/filters/duplicate.xml @@ -6,7 +6,7 @@ options that specify how duplicates will be recognized, and . Generally, at least one of these options is required. - + Using the duplicate filter to suppress points with the same name and location @@ -17,4 +17,3 @@ Generally, at least one of these options is required. gpsbabel -i gpx -f 1.gpx -f 2.gpx -x duplicate,location,shortname -o gpx -F merged_with_no_dupes.gpx - diff --git a/xmldoc/filters/height.xml b/xmldoc/filters/height.xml index 549877789..e8c058bbd 100644 --- a/xmldoc/filters/height.xml +++ b/xmldoc/filters/height.xml @@ -8,15 +8,13 @@ The height filter allows for the correction of these altitude values. This filte and . At least one of these options is required, both can be combined. - + This option subtracts the WGS84 geoid height from every altitude. For GPS receivers like the iBlue747 the result is the height above mean see level. gpsbabel -i gpx -f in.gpx -x height,wgs84tomsl -o gpx -F out.gpx The coordinates and altitude vales must be based an the WGS84 ellipsoid for this option to produce sensible results - + This options adds a constant value to every altitude. gpsbabel -i gpx -f in.gpx -x height,add=10.2f -o gpx -F out.gpx You can specify negative numbers to subtract the value. If no unit is specified meters are assumed. For feet you can attach an "f" to the value. - - diff --git a/xmldoc/filters/interpolate.xml b/xmldoc/filters/interpolate.xml index 174d48b29..05f6ae2e8 100644 --- a/xmldoc/filters/interpolate.xml +++ b/xmldoc/filters/interpolate.xml @@ -6,7 +6,7 @@ line (actually a great circle) between the adjacent points. You must specify either the or the option. - + Using the interpolate filter This command line reads track.gpx and inserts points wherever two adjacent diff --git a/xmldoc/filters/nuketypes.xml b/xmldoc/filters/nuketypes.xml index 4bad55ed3..81d838168 100644 --- a/xmldoc/filters/nuketypes.xml +++ b/xmldoc/filters/nuketypes.xml @@ -3,7 +3,7 @@ There are three main types of data that GPSBabel deals with: waypoints, tracks, and routes. The nuketypes filter allows removing all the data of any or all of those three types. - + Filtering data types with nuketypes If you have a GPX file that contains routes, tracks, and @@ -13,4 +13,3 @@ with this command: gpsbabel -i gpx -f bigfile.gpx -x nuketypes,waypoints,routes -o gpx -F tracksonly.gpx - diff --git a/xmldoc/filters/options/arc-distance.xml b/xmldoc/filters/options/arc-distance.xml index 8942edf78..b2ce7b246 100644 --- a/xmldoc/filters/options/arc-distance.xml +++ b/xmldoc/filters/options/arc-distance.xml @@ -11,4 +11,3 @@ points that are further away are discarded. Distances may be specified in miles (3M) or kilometers (5K). If no units are specified, the distance is assumed to be in miles. - diff --git a/xmldoc/filters/options/arc-exclude.xml b/xmldoc/filters/options/arc-exclude.xml index 5a5e7a10f..e366f1dc7 100644 --- a/xmldoc/filters/options/arc-exclude.xml +++ b/xmldoc/filters/options/arc-exclude.xml @@ -3,4 +3,3 @@ When this option is specified, the usual sense of the arc filter is reversed. That is, points that are closer than distance are discarded while points that are further away are kept. - diff --git a/xmldoc/filters/options/arc-file.xml b/xmldoc/filters/options/arc-file.xml index 963bb3632..a4012a887 100644 --- a/xmldoc/filters/options/arc-file.xml +++ b/xmldoc/filters/options/arc-file.xml @@ -7,4 +7,3 @@ GPSBabel supports converting any route or track to a file usable by this filter; simply read it in the normal way and write it using the arc file format. - diff --git a/xmldoc/filters/options/arc-points.xml b/xmldoc/filters/options/arc-points.xml index 3a916a5eb..cc7d63e5c 100644 --- a/xmldoc/filters/options/arc-points.xml +++ b/xmldoc/filters/options/arc-points.xml @@ -8,4 +8,3 @@ the lines between points are also kept. This option makes the arc filter act like a multi-point version of the radius filter. - diff --git a/xmldoc/filters/options/bend-distance.xml b/xmldoc/filters/options/bend-distance.xml index a1342200d..45dac5a1a 100644 --- a/xmldoc/filters/options/bend-distance.xml +++ b/xmldoc/filters/options/bend-distance.xml @@ -3,5 +3,3 @@ The new points will be created at this distance. The first one in the direction of the previous point, ant the second one in the direction of the next point in the route. - - diff --git a/xmldoc/filters/options/bend-minangle.xml b/xmldoc/filters/options/bend-minangle.xml index 824cc1e63..5fac76de4 100644 --- a/xmldoc/filters/options/bend-minangle.xml +++ b/xmldoc/filters/options/bend-minangle.xml @@ -4,4 +4,3 @@ greater than this value. This avoids replacing a point if the GPS unit is already pointing in the correct direction, or if the route reaches a certain point and goes back the same road. - diff --git a/xmldoc/filters/options/discard-elemax.xml b/xmldoc/filters/options/discard-elemax.xml index 98887aba5..76a7c548c 100644 --- a/xmldoc/filters/options/discard-elemax.xml +++ b/xmldoc/filters/options/discard-elemax.xml @@ -1,4 +1,3 @@ This option drops waypoints with an altitude higher than the specified value (in meters). See elemin for an explanation why this may be useful. - diff --git a/xmldoc/filters/options/discard-hdop.xml b/xmldoc/filters/options/discard-hdop.xml index 6310fb5d9..60aeeca49 100644 --- a/xmldoc/filters/options/discard-hdop.xml +++ b/xmldoc/filters/options/discard-hdop.xml @@ -4,4 +4,3 @@ Precision (HDOP). By default, any point with an HDOP in excess of this value will be discarded regardless of its VDOP, but see . - diff --git a/xmldoc/filters/options/discard-matchcmt.xml b/xmldoc/filters/options/discard-matchcmt.xml index e14cc6472..42f756a01 100644 --- a/xmldoc/filters/options/discard-matchcmt.xml +++ b/xmldoc/filters/options/discard-matchcmt.xml @@ -1,4 +1,3 @@ Like , but instead matches on the comment. - diff --git a/xmldoc/filters/options/discard-matchname.xml b/xmldoc/filters/options/discard-matchname.xml index 40e820eb9..9ec4d977f 100644 --- a/xmldoc/filters/options/discard-matchname.xml +++ b/xmldoc/filters/options/discard-matchname.xml @@ -2,7 +2,7 @@ This option discards points that have shortnames that match the provided regular expression. - + Discarding specific point by regular expression For example geocaches typically have names starting with GC followed diff --git a/xmldoc/filters/options/discard-sat.xml b/xmldoc/filters/options/discard-sat.xml index dd7cfb361..4468d7848 100644 --- a/xmldoc/filters/options/discard-sat.xml +++ b/xmldoc/filters/options/discard-sat.xml @@ -1,4 +1,3 @@ This option specifies the minimum required number of satellites. - diff --git a/xmldoc/filters/options/discard-vdop.xml b/xmldoc/filters/options/discard-vdop.xml index 30aebdb28..2d1cd9539 100644 --- a/xmldoc/filters/options/discard-vdop.xml +++ b/xmldoc/filters/options/discard-vdop.xml @@ -4,4 +4,3 @@ Precision (VDOP). By default, any point with an VDOP in excess of this value will be discarded regardless of its HDOP, but see . - diff --git a/xmldoc/filters/options/duplicate-all.xml b/xmldoc/filters/options/duplicate-all.xml index 4eaa052f9..7814d77a5 100644 --- a/xmldoc/filters/options/duplicate-all.xml +++ b/xmldoc/filters/options/duplicate-all.xml @@ -5,7 +5,7 @@ your input file contains waypoints A, B, B, and C, the output file will contain waypoints A, B, and C without the option, or just A and C with the option. - + Using the duplicate filter to implement an "ignore list." This option may be used to implement an "ignore list." In the following @@ -14,4 +14,3 @@ ignored from a larger collection of waypoints: gpsbabel -i gpx -f waypoints.gpx -i csv -f to_ignore.csv -x duplicate,shortname,all -o gpx -F filtered.gpx - diff --git a/xmldoc/filters/options/duplicate-correct.xml b/xmldoc/filters/options/duplicate-correct.xml index a1d809700..5a17b72d8 100644 --- a/xmldoc/filters/options/duplicate-correct.xml +++ b/xmldoc/filters/options/duplicate-correct.xml @@ -8,7 +8,7 @@ longitude in the original waypoint. As an example, this option may be used to adjust the locations of "puzzle" geocaches in a Groundspeak pocket query: - + Using the duplicate filter to correct the locations of "puzzle" geocaches gpsbabel -i gpx -f 43622.gpx -i csv -f corrections.csv -x duplicate,shortname,correct -o gpx -F 43622-corrected.gpx diff --git a/xmldoc/filters/options/duplicate-location.xml b/xmldoc/filters/options/duplicate-location.xml index 67b040ba6..74bed1eda 100644 --- a/xmldoc/filters/options/duplicate-location.xml +++ b/xmldoc/filters/options/duplicate-location.xml @@ -6,4 +6,3 @@ names are not expected to be the same. It also might be used along with the option to remove duplicate waypoints if the names of several unrelated groups of waypoints might be the same. - diff --git a/xmldoc/filters/options/duplicate-shortname.xml b/xmldoc/filters/options/duplicate-shortname.xml index d24ff392b..d9c6961a4 100644 --- a/xmldoc/filters/options/duplicate-shortname.xml +++ b/xmldoc/filters/options/duplicate-shortname.xml @@ -5,5 +5,3 @@ a short name with a waypoint that has come before. This option might be used to remove duplicates if you are merging two datasets that were each created in part from a common ancestor dataset. - - diff --git a/xmldoc/filters/options/interpolate-distance.xml b/xmldoc/filters/options/interpolate-distance.xml index 4cef24f6b..913d40df8 100644 --- a/xmldoc/filters/options/interpolate-distance.xml +++ b/xmldoc/filters/options/interpolate-distance.xml @@ -10,4 +10,3 @@ no units are specified, the units are assumed to be miles. Either this option or the must be specified. - diff --git a/xmldoc/filters/options/interpolate-time.xml b/xmldoc/filters/options/interpolate-time.xml index 4bdfe5669..9cc27e38c 100644 --- a/xmldoc/filters/options/interpolate-time.xml +++ b/xmldoc/filters/options/interpolate-time.xml @@ -9,4 +9,3 @@ This value is always specified in units of seconds. Either this option or the must be specified. - diff --git a/xmldoc/filters/options/nuketypes-routes.xml b/xmldoc/filters/options/nuketypes-routes.xml index 9c70b59ba..42668f613 100644 --- a/xmldoc/filters/options/nuketypes-routes.xml +++ b/xmldoc/filters/options/nuketypes-routes.xml @@ -1,4 +1,3 @@ This option causes the nuketypes filter to discard all route data. - diff --git a/xmldoc/filters/options/nuketypes-tracks.xml b/xmldoc/filters/options/nuketypes-tracks.xml index 536c9d6cc..0ae63279d 100644 --- a/xmldoc/filters/options/nuketypes-tracks.xml +++ b/xmldoc/filters/options/nuketypes-tracks.xml @@ -1,4 +1,3 @@ This option causes the nuketypes filter to discard all track data. - diff --git a/xmldoc/filters/options/nuketypes-waypoints.xml b/xmldoc/filters/options/nuketypes-waypoints.xml index 00edd4bd2..e81602012 100644 --- a/xmldoc/filters/options/nuketypes-waypoints.xml +++ b/xmldoc/filters/options/nuketypes-waypoints.xml @@ -2,4 +2,3 @@ This option causes the nuketypes filter to discard all waypoints that are not associated with a track or route. - diff --git a/xmldoc/filters/options/polygon-exclude.xml b/xmldoc/filters/options/polygon-exclude.xml index cce1cd82f..efee6e045 100644 --- a/xmldoc/filters/options/polygon-exclude.xml +++ b/xmldoc/filters/options/polygon-exclude.xml @@ -3,4 +3,3 @@ When this option is specified, the usual sense of the polygon filter is reversed. That is, points that are inside the polygon are discarded while points that are further away are kept. - diff --git a/xmldoc/filters/options/polygon-file.xml b/xmldoc/filters/options/polygon-file.xml index 31a967c28..57376b039 100644 --- a/xmldoc/filters/options/polygon-file.xml +++ b/xmldoc/filters/options/polygon-file.xml @@ -13,4 +13,3 @@ need to make sure that the first point and the last point in the file are the same, as the polygon filter depends on that. You can do so with any text editor. - diff --git a/xmldoc/filters/options/position-all.xml b/xmldoc/filters/options/position-all.xml index 16e59e5a8..79744ddc2 100644 --- a/xmldoc/filters/options/position-all.xml +++ b/xmldoc/filters/options/position-all.xml @@ -5,4 +5,3 @@ the specified distance of one another, rather than leaving just one of them. This option may be used to entirely remove clusters of points. - diff --git a/xmldoc/filters/options/position-distance.xml b/xmldoc/filters/options/position-distance.xml index d85b1762a..03bc9be0e 100644 --- a/xmldoc/filters/options/position-distance.xml +++ b/xmldoc/filters/options/position-distance.xml @@ -6,4 +6,3 @@ two points are closer than this distance, only one of them is kept. Distances may be expressed in feet (30f) or meters (10m). If no unit is specified, the distance is assumed to be in feet. - diff --git a/xmldoc/filters/options/radius-asroute.xml b/xmldoc/filters/options/radius-asroute.xml index aff16e2be..e93230927 100644 --- a/xmldoc/filters/options/radius-asroute.xml +++ b/xmldoc/filters/options/radius-asroute.xml @@ -9,5 +9,3 @@ Note that this route is not necessarily the most efficient route to visit all of the points. In fact, for some data sets, it might be the least efficient route. - - diff --git a/xmldoc/filters/options/radius-maxcount.xml b/xmldoc/filters/options/radius-maxcount.xml index 1a228e08a..d122665b2 100644 --- a/xmldoc/filters/options/radius-maxcount.xml +++ b/xmldoc/filters/options/radius-maxcount.xml @@ -19,4 +19,3 @@ otherwise throw away. You will still get no more than maxcount points, but they will all be at least distance away from the center. (And possibly sorted.) - diff --git a/xmldoc/filters/options/radius-nosort.xml b/xmldoc/filters/options/radius-nosort.xml index 42ba6d5e5..91c1c7248 100644 --- a/xmldoc/filters/options/radius-nosort.xml +++ b/xmldoc/filters/options/radius-nosort.xml @@ -3,4 +3,3 @@ If this option is specified, the radius filter will not sort the remaining points by distance from the center. They will remain in whatever order they were originally. - diff --git a/xmldoc/filters/options/simplify-crosstrack.xml b/xmldoc/filters/options/simplify-crosstrack.xml index eb7600f0c..7ac8ca2a9 100644 --- a/xmldoc/filters/options/simplify-crosstrack.xml +++ b/xmldoc/filters/options/simplify-crosstrack.xml @@ -8,4 +8,3 @@ between the two points adjacent to it. If neither this option nor the option is specified, this is the default. - diff --git a/xmldoc/filters/options/stack-replace.xml b/xmldoc/filters/options/stack-replace.xml index 59bcefe2e..2a088ded5 100644 --- a/xmldoc/filters/options/stack-replace.xml +++ b/xmldoc/filters/options/stack-replace.xml @@ -5,4 +5,3 @@ should never need to specify it, but it is included for the sake of readability. When this option is specified, the popped state replaces the current state. - diff --git a/xmldoc/filters/options/stack-swap.xml b/xmldoc/filters/options/stack-swap.xml index b96874456..64b249111 100644 --- a/xmldoc/filters/options/stack-swap.xml +++ b/xmldoc/filters/options/stack-swap.xml @@ -7,4 +7,3 @@ state from the stack. By default, it is swapped with the top of the stack, but the can be used to specify a different saved state. - diff --git a/xmldoc/filters/options/track-course.xml b/xmldoc/filters/options/track-course.xml index 1de9c41ea..345cb461f 100644 --- a/xmldoc/filters/options/track-course.xml +++ b/xmldoc/filters/options/track-course.xml @@ -7,4 +7,3 @@ filter. The heading at each trackpoint is simply the course from the previous trackpoint in the track. The first trackpoint in each track is arbitrarily assigned a heading of 0 degrees. - diff --git a/xmldoc/filters/options/track-discard.xml b/xmldoc/filters/options/track-discard.xml index a77b79dad..5db143afc 100644 --- a/xmldoc/filters/options/track-discard.xml +++ b/xmldoc/filters/options/track-discard.xml @@ -2,11 +2,10 @@ This option is used in conjunction with the merge option to discard track points with missing timestamps instead of aborting with the "Found track point at lat,lon without time!" error. - + Merging tracks with missing timestamps with the track filter Suppose you want to merge tracks that may have missing timestamps. To do that, use this command line: gpsbabel -t -i gpx -f john.gpx -f doe.gpx -x track,merge,discard -o gpx -F john_doe.gpx - diff --git a/xmldoc/filters/options/track-faketime.xml b/xmldoc/filters/options/track-faketime.xml index 15955ffc2..0e7bd37b1 100644 --- a/xmldoc/filters/options/track-faketime.xml +++ b/xmldoc/filters/options/track-faketime.xml @@ -21,7 +21,7 @@ The specification of the steptime is optional. The parameter was added because some software products (e.g. garmin training center) require a time value for each trackpoint. - + Replace time values of a track Replace all time values with new time values. @@ -30,7 +30,7 @@ increment 2 seconds between each trackpoint: gpsbabel -i kml -f in.kml -x track,faketime=f20100705200000+2 -o gtrnctr -F out.tcx - + Add time values to a track Add a time value to a trackpoint, if the trackpoint contains no time value. diff --git a/xmldoc/filters/options/track-fix.xml b/xmldoc/filters/options/track-fix.xml index 7b843b4de..ed195cdd1 100644 --- a/xmldoc/filters/options/track-fix.xml +++ b/xmldoc/filters/options/track-fix.xml @@ -6,4 +6,3 @@ value. Valid values for this option are PPS, DGPS, 3D, 2D, or NONE. This option is most useful when converting from a format that doesn't contain GPS fix status to one that requires it. - diff --git a/xmldoc/filters/options/track-merge.xml b/xmldoc/filters/options/track-merge.xml index 7b9e4ceb2..f6e08f361 100644 --- a/xmldoc/filters/options/track-merge.xml +++ b/xmldoc/filters/options/track-merge.xml @@ -2,7 +2,7 @@ This option puts all track points from all tracks into a single track and sorts them by time stamp. Redundant points with identical time stamps will be dropped. - + Merging tracks with the track filter Suppose you want to merge tracks recorded with two different GPS devices @@ -10,4 +10,3 @@ at the same time. To do that, use this command line: gpsbabel -t -i gpx -f john.gpx -i gpx -f doe.gpx -x track,merge,title="COMBINED LOG" -o gpx -F john_doe.gpx - diff --git a/xmldoc/filters/options/track-move.xml b/xmldoc/filters/options/track-move.xml index e3dd19ff7..c7a09cb84 100644 --- a/xmldoc/filters/options/track-move.xml +++ b/xmldoc/filters/options/track-move.xml @@ -10,14 +10,14 @@ leading '+' or '-' sign. Positive integers shift the tracks later, while negati the tracks earlier. If no sign is provided the integer is assumed to be nonnegative. Possible units are w for weeks, d for days, h for hours, m for minutes and s for seconds. - + Time-shifting a track with the track filter The following command line will shift all tracks to be one hour later. gpsbabel -t -i gpx -f in.gpx -x track,move=+1h -o gpx -F out.gpx - + Time-shifting a track with the track filter to correct WNRO The following command line will shift all tracks to be 1024 weeks later. Because the GPS Week Number @@ -26,7 +26,7 @@ a multiple of 1024 weeks. gpsbabel -t -i gpx -f in.gpx -x track,move=+1024w -o gpx -F out.gpx - + Time-shifting a track with the track filter with combined units The following command lines will each shift all tracks to be 1 hour and 1 minute earlier, i.e. 61 minutes earlier. @@ -34,4 +34,3 @@ The following command lines will each shift all tracks to be 1 hour and 1 minute gpsbabel -t -i gpx -f in.gpx -x track,move=-1h-1m -o gpx -F out.gpx gpsbabel -t -i gpx -f in.gpx -x track,move=-61m -o gpx -F out.gpx - diff --git a/xmldoc/filters/options/track-name.xml b/xmldoc/filters/options/track-name.xml index 930b88bf7..0adde0699 100644 --- a/xmldoc/filters/options/track-name.xml +++ b/xmldoc/filters/options/track-name.xml @@ -4,4 +4,3 @@ With the name option you can filter out a track by title. The comparison is always non-case-sensitive. Wildcards are allowed. - diff --git a/xmldoc/filters/options/track-sdistance.xml b/xmldoc/filters/options/track-sdistance.xml index 89060b6ea..0846b6b01 100644 --- a/xmldoc/filters/options/track-sdistance.xml +++ b/xmldoc/filters/options/track-sdistance.xml @@ -32,5 +32,3 @@ gpsbabel -t -x track,pack,sdistance=0.3k,split=5m -o gpx -F out.gpx - - diff --git a/xmldoc/filters/options/track-start.xml b/xmldoc/filters/options/track-start.xml index 0ead2bd56..bb61ae634 100644 --- a/xmldoc/filters/options/track-start.xml +++ b/xmldoc/filters/options/track-start.xml @@ -14,7 +14,7 @@ not necessary to specify the smaller time units if they are not needed. That is, if you only care about points logged between 10 AM and 6 PM on a given date, you need not specify the minutes or seconds. - + Extracting a period of time with the track filter To get only the parts of a track that were mapped on 20 July 2005 diff --git a/xmldoc/filters/options/track-stop.xml b/xmldoc/filters/options/track-stop.xml index 4ec4b09eb..5106461b4 100644 --- a/xmldoc/filters/options/track-stop.xml +++ b/xmldoc/filters/options/track-stop.xml @@ -12,4 +12,3 @@ The time for this option is expressed in UTC. See the option for the format of this value and an example of usage. - diff --git a/xmldoc/filters/options/transform-del.xml b/xmldoc/filters/options/transform-del.xml index aceaf77fa..ed3cb652c 100644 --- a/xmldoc/filters/options/transform-del.xml +++ b/xmldoc/filters/options/transform-del.xml @@ -3,7 +3,7 @@ This option, when used in connection with the wpt, rte, or trk options, tells GPSBabel to delete the source data after conversion. This is most useful if you are trying to avoid duplicated data in the output. - + Convert a GPX track to GPX waypoints, tossing the original track gpsbabel -i gpx -f blah.gpx -x transform,wpt=trk,del -o gpx -F converted.gpx diff --git a/xmldoc/filters/options/transform-rptdigits.xml b/xmldoc/filters/options/transform-rptdigits.xml index b6333fc46..cb735678d 100644 --- a/xmldoc/filters/options/transform-rptdigits.xml +++ b/xmldoc/filters/options/transform-rptdigits.xml @@ -7,7 +7,7 @@ When GPSBabel creates route points during the transformation process these point Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option. - + Convert a GPX track to a GPX route, deleting the original track, using 2 digits for the generated numbers. gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptdigits=2 -o gpx -F route.gpx diff --git a/xmldoc/filters/options/transform-rptname.xml b/xmldoc/filters/options/transform-rptname.xml index 4df5c9257..8d74bc38b 100644 --- a/xmldoc/filters/options/transform-rptname.xml +++ b/xmldoc/filters/options/transform-rptname.xml @@ -6,7 +6,7 @@ GPSBabel creates route points during the transformation process named "RPTnnn" w Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes. - + Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name. gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx diff --git a/xmldoc/filters/options/transform-rte.xml b/xmldoc/filters/options/transform-rte.xml index 85986c2a9..8b57c6ac6 100644 --- a/xmldoc/filters/options/transform-rte.xml +++ b/xmldoc/filters/options/transform-rte.xml @@ -1,7 +1,7 @@ This option selects the destination type of this filter to be routes. Choose this when you want to convert tracks into waypoints routes. A single route will be created in the sequence they appear in the input. - + Converting a pile of waypoints to a GPX route Say you you have a data file that came from CSV file that you want to convert diff --git a/xmldoc/filters/options/transform-trk.xml b/xmldoc/filters/options/transform-trk.xml index 3f5475977..1b5af18fd 100644 --- a/xmldoc/filters/options/transform-trk.xml +++ b/xmldoc/filters/options/transform-trk.xml @@ -3,7 +3,7 @@ This option selects the destination type of this filter to be tracks. Choose this when you want to create tracks from a list of waypoints or routes. A single track will be created in the sequence they appear in the input. - + Converting a pile of waypoints to a GPX track Say you you have a data file that came from CSV file that you want to convert diff --git a/xmldoc/filters/options/transform-wpt.xml b/xmldoc/filters/options/transform-wpt.xml index 45c9f0a88..6e530c5c3 100644 --- a/xmldoc/filters/options/transform-wpt.xml +++ b/xmldoc/filters/options/transform-wpt.xml @@ -2,7 +2,7 @@ This option selects the destination type of this filter to be waypoints. Choose this when you want to convert tracks or routes into waypoints. - + Converting a track to a sequence of waypoints Say you you have a KML file that contains a track but you want to convert it to a CSV file that can contain only waypoints, perhaps to import into a spreadsheet. Use the following command: diff --git a/xmldoc/filters/polygon.xml b/xmldoc/filters/polygon.xml index d36012061..a06419b6e 100644 --- a/xmldoc/filters/polygon.xml +++ b/xmldoc/filters/polygon.xml @@ -6,7 +6,7 @@ that the arc it describes must be a closed cycle. That is, for a simple polygon, the first and last points must be the same. Here's a square: - + # A square (not really) polygon 41.0000 -85.0000 41.0000 -86.0000 @@ -18,7 +18,7 @@ same. Here's a square: Polygons may include islands and holes. To include an island or a hole, just append it to the main polygon. - + # A square polygon with a triangular hole 41.0000 -85.0000 41.0000 -86.0000 @@ -41,7 +41,7 @@ Note that this filter currently will not work properly if your polygon contains one or both poles or if it spans the line of 180 degrees east or west longitude. - + Using the polygon filter Suppose you have a polygon file that defines the border of your county, @@ -50,7 +50,7 @@ in your county: gpsbabel -i geo -f 1.loc -x polygon,file=mycounty.txt -o mapsend -F 2.wpt - + Using the polygon and arc filters to find points in or nearly in a polygon @@ -75,4 +75,3 @@ puts the two lists together, and then filters out any points that appear twice line will be kept by both the polygon and the arc filter.) - diff --git a/xmldoc/filters/position.xml b/xmldoc/filters/position.xml index e66450b70..ef714aae5 100644 --- a/xmldoc/filters/position.xml +++ b/xmldoc/filters/position.xml @@ -4,7 +4,7 @@ For waypoints a point is removed if it is within the specified distance of a pre For routes and tracks consecutive points are removed until the distance between the bracketing points is greater than the specified distance. - + Using the position filter to suppress close points The following command removes multiple points that are within @@ -12,4 +12,3 @@ one foot of each other, leaving just one. gpsbabel -i geo -f 1.loc -f 2.loc -x position,distance=1f -o mapsend -F 3.wpt - diff --git a/xmldoc/filters/radius.xml b/xmldoc/filters/radius.xml index c2fbda597..c241d26a1 100644 --- a/xmldoc/filters/radius.xml +++ b/xmldoc/filters/radius.xml @@ -7,11 +7,10 @@ specified point will be removed from the dataset. By default, all remaining points are sorted so that points closer to the center appear earlier in the output file. - + Using the radius filter to find points close to a given point This example command line would include only points within 1 1/2 miles of N30.000 W 90.000 gpsbabel -i geo -f 1.loc -x radius,distance=1.5M,lat=30.0,lon=-90.0 -o mapsend -F 2.wpt - diff --git a/xmldoc/filters/resample.xml b/xmldoc/filters/resample.xml index b5869724d..1d6e4d717 100644 --- a/xmldoc/filters/resample.xml +++ b/xmldoc/filters/resample.xml @@ -2,7 +2,7 @@ The resampling filter can be used to change the sample rate of a track. It is intended to be used with track points that have been sampled at a constant rate. It can be used to change the sample rate by a rational factor. It can also be used to smooth a track with or without changing the sample rate. The filter works across the antimeridian. - + Interpolation with the resampling filter This examples doubles the sample rate. The data is filtered after interpolation regardless of the order of the options. @@ -10,7 +10,7 @@ This examples doubles the sample rate. The data is filtered after interpolation gpsbabel -t -i unicsv -f data.csv -x resample,interpolate=2,average=2 -o unicsv,utc=0 -F fast.csv - + Decimation with the resampling filter This examples reduces the sample rate by a factor of 4. The data is filtered before decimation regardless of the order of the options. @@ -18,11 +18,10 @@ This examples reduces the sample rate by a factor of 4. The data is filtered be gpsbabel -t -i unicsv -f data.csv -x resample,average=4,decimate=2 -o unicsv,utc=0 -F slow.csv - + Averaging with the resampling filter This examples averages the adjacent points. A running average filter of length two samples is applied in the forward and reverse directions. gpsbabel -t -i unicsv -f data.csv -x resample,average=2 -o unicsv,utc=0 -F smooth.csv - diff --git a/xmldoc/filters/reverse.xml b/xmldoc/filters/reverse.xml index 7fb303868..693664cc0 100644 --- a/xmldoc/filters/reverse.xml +++ b/xmldoc/filters/reverse.xml @@ -16,4 +16,3 @@ will be in for unpleasant ride. application cares about timestamps - diff --git a/xmldoc/filters/simplify.xml b/xmldoc/filters/simplify.xml index 7502254a2..613735db5 100644 --- a/xmldoc/filters/simplify.xml +++ b/xmldoc/filters/simplify.xml @@ -18,4 +18,3 @@ wish to use with a Magellan GPS receiver that only supports up to 50 points in a route: gpsbabel -r -i saroute -f RoadTrip.anr -x simplify,count=50 -o magellan -F grocery.rte - diff --git a/xmldoc/filters/sort.xml b/xmldoc/filters/sort.xml index 7541be0af..70646ed71 100644 --- a/xmldoc/filters/sort.xml +++ b/xmldoc/filters/sort.xml @@ -1,4 +1,3 @@ This filter sorts waypoints, routes and/or tracks by the selected field(s). - diff --git a/xmldoc/filters/stack.xml b/xmldoc/filters/stack.xml index 8760429aa..dccbbac66 100644 --- a/xmldoc/filters/stack.xml +++ b/xmldoc/filters/stack.xml @@ -46,4 +46,3 @@ gpsbabel -i gpx -f indiana.gpx -x stack,pop,append -o magellan -F fwaind.wpt - diff --git a/xmldoc/filters/track.xml b/xmldoc/filters/track.xml index e2177de75..6080aa0ec 100644 --- a/xmldoc/filters/track.xml +++ b/xmldoc/filters/track.xml @@ -4,5 +4,3 @@ WARNING: This filter always drops empty tracks. This filter performs various operations on track data. - - diff --git a/xmldoc/formats/baroiq.xml b/xmldoc/formats/baroiq.xml index 46d7d42d0..d1d827469 100644 --- a/xmldoc/formats/baroiq.xml +++ b/xmldoc/formats/baroiq.xml @@ -1,5 +1,4 @@ -Serial download protocol for the Brauniger IQ series of +Serial download protocol for the Brauniger IQ series of barograph recording flight instruments. This format creates a track of altitude vs time which can be merged with a GPS track of the same flight to create a three dimensional IGC file. - diff --git a/xmldoc/formats/cambridge.xml b/xmldoc/formats/cambridge.xml index e1f20a899..8334f87f7 100644 --- a/xmldoc/formats/cambridge.xml +++ b/xmldoc/formats/cambridge.xml @@ -2,7 +2,6 @@ Support for -Cambridge -and Winpilot +Cambridge +and Winpilot flight analysis and planning software for glider pilots. - diff --git a/xmldoc/formats/csv.xml b/xmldoc/formats/csv.xml index 660b96e13..54cf14890 100644 --- a/xmldoc/formats/csv.xml +++ b/xmldoc/formats/csv.xml @@ -1,14 +1,14 @@ There are a billion variants of Comma Separated Value -data. This is the one specifically that makes DeLorme S&A Deluxe 9 happy. It's +data. This is the one specifically that makes DeLorme S&A Deluxe 9 happy. It's also a very simple program and useful for many other programs like spreadsheets, but contains only a very minimal information. For general purpose use, you'll probably be more happy with our universal csv (unicsv) format. CSV is also the correct format for - Lowrance MapCreate, + Lowrance MapCreate, their commercial mapping program, or GDM6 (their free waypoint -manager) for iFinder which is available at lowrance.com +manager) for iFinder which is available at lowrance.com On write, this format writes simple "latitude, longitude" pairs, but @@ -18,7 +18,7 @@ on read it will read anything supported by our universal csv format. -Example 'csv' file +Example 'csv' file 35.97203, -87.13470, Mountain Bike Heaven by susy1313 36.09068, -86.67955, The Troll by a182pilot & Family diff --git a/xmldoc/formats/custom.xml b/xmldoc/formats/custom.xml index 595333d8f..594376fed 100644 --- a/xmldoc/formats/custom.xml +++ b/xmldoc/formats/custom.xml @@ -5,5 +5,5 @@ for debugging purposes when developing a new format module for GPSBabel. To understand the contents of this file, look at the style/custom.style file in the GPSBabel source -distribution as well as . +distribution as well as . diff --git a/xmldoc/formats/dg-100.xml b/xmldoc/formats/dg-100.xml index d34baa6f6..a0fea9a00 100644 --- a/xmldoc/formats/dg-100.xml +++ b/xmldoc/formats/dg-100.xml @@ -1,7 +1,7 @@ - Serial download protocol for the GlobalSat DG-100, - GlobalSat BT-335, - and GlboalSat BT-338XGPS data loggers. + Serial download protocol for the GlobalSat DG-100, + GlobalSat BT-335, + and GlboalSat BT-338XGPS data loggers. While the DG-100 has a button to record waypoints, they seem to be indistinguishable @@ -9,13 +9,13 @@ regardless of whether they were recorded automatically or manually. - GlobalSat DG-100 + GlobalSat DG-100 - + Command showing DG-100 download and erase on Linux gpsbabel -t -i dg-100,erase -o gpx /dev/ttyUSB0 outputfile.gpx - + Command showing DG-100 erase_only option on Linux gpsbabel -t -i dg-100,erase_only /dev/ttyUSB0 diff --git a/xmldoc/formats/dg-200.xml b/xmldoc/formats/dg-200.xml index bde00c63a..041520c2f 100644 --- a/xmldoc/formats/dg-200.xml +++ b/xmldoc/formats/dg-200.xml @@ -1,12 +1,12 @@ -Serial download protocol for the GlobalSat DG-200GPS data loggers. +Serial download protocol for the GlobalSat DG-200GPS data loggers. -GlobalSat DG-200 +GlobalSat DG-200 - + Command showing DG-200 download and erase on Linux gpsbabel -t -i dg-200,erase -o gpx /dev/ttyUSB0 outputfile.gpx - + Command showing DG-200 erase_only option on Linux gpsbabel -t -i dg-200,erase_only /dev/ttyUSB0 @@ -20,4 +20,3 @@ but unfortunately their driver has a defect which makes it unstable with GPSBabel. - diff --git a/xmldoc/formats/exif.xml b/xmldoc/formats/exif.xml index b5381f8bd..81195317b 100644 --- a/xmldoc/formats/exif.xml +++ b/xmldoc/formats/exif.xml @@ -1,6 +1,6 @@ This format reads and writes GPS information embedded in - EXIF, + EXIF, the Exchangeable Image Format, data. EXIF is a standardized method of encoding data in pictures such as JPEG, TIFF, and WAV and is frequently used by mobile phones with cameras and cameras with built-in GPS. @@ -9,4 +9,3 @@ EXIF is frequently used for Geolocating photographs so their images can be correlated with time and location. - diff --git a/xmldoc/formats/garmin.xml b/xmldoc/formats/garmin.xml index 9960c32d1..e27c6edc4 100644 --- a/xmldoc/formats/garmin.xml +++ b/xmldoc/formats/garmin.xml @@ -11,7 +11,7 @@ Supported Garmin GPS receivers with USB include - + Astro Edge 205 Edge 305 @@ -33,7 +33,7 @@ Forerunner 305 Foretrex 201 Foretrex 301 -GPS 18This model does not support transfer of waypoints, tracks, or routes, but may be used with the realtime tracking feature. +GPS 18This model does not support transfer of waypoints, tracks, or routes, but may be used with the realtime tracking feature. GPSMAP 195 GPSMAP 276C GPSMAP 295 @@ -76,14 +76,14 @@ the following Bluetooth Garmin products: - + GPS 10 and most serial Garmin GPS receivers including: - + eMap eTrex Camo eTrex Legend @@ -118,7 +118,7 @@ The following Garmin GPS receivers are supported, but they do not support Garmin communication protocol and don't work with the option. To use these receivers, read or write GPX files from the mass storage device as mounted on your computer. - + eTrex 10 eTrex 20 eTrex 30 @@ -154,7 +154,7 @@ GPX files from the mass storage device as mounted on your computer. Nuvi 260W Nuvi 270 Nuvi 275T -Nuvi 300This unit uses GPX format, not Garmin protocol. Therefore one should communicate with it by reading and writing GPX files instead of using this format. Members of this class of products do not support realtime positioning protocol. +Nuvi 300This unit uses GPX format, not Garmin protocol. Therefore one should communicate with it by reading and writing GPX files instead of using this format. Members of this class of products do not support realtime positioning protocol. Nuvi 310 Nuvi 350 Nuvi 370 @@ -297,7 +297,7 @@ so they are named 'Custom 0' through 'Custom 511'. filename. For this to work on Windows, you must install the Garmin driver. For Linux, this will fail if you have the garmin_gps kernel module loaded. - See the Operating System Notes for details. + See the Operating System Notes for details. @@ -312,7 +312,7 @@ communications protocol and are not supported by GPSBabel. Marine plotters: - + GPSMap 420 GPSMap 430 GPSMap 440 @@ -329,7 +329,7 @@ Marine plotters: The PDA products - + iQue 3000 iQue 3200 iQue 3600 diff --git a/xmldoc/formats/garmin301.xml b/xmldoc/formats/garmin301.xml index 9c64d5067..72053e4d5 100644 --- a/xmldoc/formats/garmin301.xml +++ b/xmldoc/formats/garmin301.xml @@ -3,11 +3,11 @@ is most useful for exporting data from units that support heart rate data such as - Garmin Forerunner 301, - Garmin Forerunner 305, and - Garmin Edge 305, and + Garmin Forerunner 301, + Garmin Forerunner 305, and + Garmin Edge 305, and to other programs for analysis. It's a simple comma delimited format that includes the timestamp, 3D position information and heart rate so you can pull it into a spreadsheet or graphing program. - \ No newline at end of file + diff --git a/xmldoc/formats/garmin_fit.xml b/xmldoc/formats/garmin_fit.xml index 1f7d8c50f..8dd9b0e58 100644 --- a/xmldoc/formats/garmin_fit.xml +++ b/xmldoc/formats/garmin_fit.xml @@ -1,10 +1,10 @@ GPSBabel supports reading and writing of tracks in the .fit format used by products based on the Garmin -ANT+ protocol. +ANT+ protocol. -As in case of Garmin Training Center, +As in case of Garmin Training Center, FIT files contain courses with laps etc. which don't exactly match GPSBabel's waypoints, tracks, and routes. An attempt is made to extract and transform data than can be handled by GPSBabel like heart rate etc. and @@ -20,7 +20,7 @@ inserting them at the nearest location in the track/course. By default, generic course points are written unless the waypoint name contains one of the following words in which case course points of type left/right are emitted: - + left, links, gauche, izquierda, sinistra right, rechts, droit, derecha, destro diff --git a/xmldoc/formats/garmin_gpi.xml b/xmldoc/formats/garmin_gpi.xml index d46b8494e..1ae475098 100644 --- a/xmldoc/formats/garmin_gpi.xml +++ b/xmldoc/formats/garmin_gpi.xml @@ -1,7 +1,7 @@ The format garmin_gpi supports the binary POI (.gpi) files that are usable on newer Garmin GPS receivers. See garmin_poi for additional information about Garmin's own Poiloader program. - Garmin POI-Loader is the standard application that creates GPI files + Garmin POI-Loader is the standard application that creates GPI files with all possible features. @@ -44,7 +44,7 @@ directly. - + Command showing garmin_gpi output example diff --git a/xmldoc/formats/garmin_poi.xml b/xmldoc/formats/garmin_poi.xml index 7e0471a4d..f8e6d5b50 100644 --- a/xmldoc/formats/garmin_poi.xml +++ b/xmldoc/formats/garmin_poi.xml @@ -1,5 +1,5 @@ - The Garmin POI loader + The Garmin POI loader loads custom points of interest into certain models of Garmin GPS receivers. (As of this writing, only the models introduced in 2005 and later are supported. See Garmin's site for more info.) diff --git a/xmldoc/formats/garmin_txt.xml b/xmldoc/formats/garmin_txt.xml index 62111d44d..42d30a97c 100644 --- a/xmldoc/formats/garmin_txt.xml +++ b/xmldoc/formats/garmin_txt.xml @@ -1,23 +1,22 @@ This is a textual format that contains nearly all of the information -contained in the MapSource main format, GDB. +contained in the MapSource main format, GDB. This format also contains some computed values such as distances between routepoints and trackpoints, speed, and course (heading). The main goal of garmin_txt is to make aviation data more available. Because -MapSource supports only the export, GPSBabel gives you the possibility to -bring aviation data into MapSource. +MapSource supports only the export, GPSBabel gives you the possibility to +bring aviation data into MapSource. -During the export with MapSource, some fields are written using local settings -of MapSource and Windows. These include grid format, gps datum, distance and +During the export with MapSource, some fields are written using local settings +of MapSource and Windows. These include grid format, gps datum, distance and temperature units, and the representation of date and time fields. GPSBabel tries to read all items automatically. Problems with date and time format can be solved with the 'date' and 'time' options. - + Command showing garmin_txt output with all options gpsbabel -i garmin_txt,date="MM/DD/YYYY",time="hh:mm:ss xx" -f in.txt -o garmin_txt,date="DD.MM.YYYY",datum="WGS 72",dist=m,prec=6,temp=c,time="HH:mm:ss",utc=+2 -F out.txt - diff --git a/xmldoc/formats/gdb.xml b/xmldoc/formats/gdb.xml index a26113653..ed98f5d91 100644 --- a/xmldoc/formats/gdb.xml +++ b/xmldoc/formats/gdb.xml @@ -1,13 +1,12 @@ Support for the "Garmin GPS Database" format used by - default in MapSource versions since release 6.0 of + default in MapSource versions since release 6.0 of that product. By default GPSBabel creates gdb files of version 2. Version 2 is used in Mapsource 6.3 and 6.5. This format - is also used by Garmin BaseCamp for Mac and Windows. + is also used by Garmin BaseCamp for Mac and Windows. Garmin GPS database is an undocumented file format. The basic info for this module came from the existing MapSource conversion code. - diff --git a/xmldoc/formats/geojson.xml b/xmldoc/formats/geojson.xml index 1f7d238d8..8b3891746 100644 --- a/xmldoc/formats/geojson.xml +++ b/xmldoc/formats/geojson.xml @@ -1,5 +1,5 @@ -This module supports a subset of the GeoJSON format. +This module supports a subset of the GeoJSON format. GeoJSON is a poor fit for GPSBabel's internal data structures as GPSBabel @@ -22,9 +22,9 @@ The potentially nested/recursive nature of GeoJSON in general would be an awkward implementation. -Initial development was free-handed by looking at the GeoJSON RFC. Corner cases were handled by -using GDAL's ogr2ogr +Initial development was free-handed by looking at the GeoJSON RFC. Corner cases were handled by +using GDAL's ogr2ogr to convert GPX to JSON and compare the output. The results were then - JSON validated and viewed on - JSON web viewer. + JSON validated and viewed on + JSON web viewer. diff --git a/xmldoc/formats/globalsat.xml b/xmldoc/formats/globalsat.xml index d4cf0e7c8..b25fb655a 100644 --- a/xmldoc/formats/globalsat.xml +++ b/xmldoc/formats/globalsat.xml @@ -1,5 +1,5 @@ - Serial download protocol for the GlobalSat Sport gh625XT training watch. + Serial download protocol for the GlobalSat Sport gh625XT training watch. The GlobalSat Sport GPS training device present themselves as USBserial devices. @@ -10,11 +10,11 @@ USB cable to your computer and the device will show up as a serial device. GlobalSat sport gh625XT gpsbabel -i globalsat -f /dev/ttyUSB0 -o gpx,garminextensions -F outfile.gpx - + Command showing list of tracks on device gpsbabel -i globalsat,showlist=1 -f /dev/ttyUSB0 - + Command track can be used to fetch a single track, default is all tracks gpsbabel -i globalsat,track=number -f /dev/ttyUSB0 -o gpx,garminextensions -F outfile.gpx @@ -26,6 +26,3 @@ USB cable to your computer and the device will show up as a serial device. that data as a serial port to software like GPSBabel. Such software comes with the unit for Windows or can be downloaded. - - - diff --git a/xmldoc/formats/gpsdrive.xml b/xmldoc/formats/gpsdrive.xml index 2f6c7a806..13b8afde5 100644 --- a/xmldoc/formats/gpsdrive.xml +++ b/xmldoc/formats/gpsdrive.xml @@ -2,6 +2,5 @@ GpsDrive way.txt file format. A space separated format -file. Tested against GpsDrive v 1.30 found at gpsdrive.de. +file. Tested against GpsDrive v 1.30 found at gpsdrive.de. Contributed by Alan Curry. - diff --git a/xmldoc/formats/gpsdrivetrack.xml b/xmldoc/formats/gpsdrivetrack.xml index 9e26a08bf..cdc4fba77 100644 --- a/xmldoc/formats/gpsdrivetrack.xml +++ b/xmldoc/formats/gpsdrivetrack.xml @@ -4,4 +4,3 @@ Format used by GpsDrive to save tracks. Like GPSDRIVE a space separated format file. See above for a link to GpsDrive. Contributed by Tobias Minich. - diff --git a/xmldoc/formats/gpssim.xml b/xmldoc/formats/gpssim.xml index c318310ff..320c51d1a 100644 --- a/xmldoc/formats/gpssim.xml +++ b/xmldoc/formats/gpssim.xml @@ -1,9 +1,9 @@ This is a write-only format used to feed waypoints, tracks, and routes - into Franson Technolgies' - GpsGate simulator. + into Franson Technolgies' + GpsGate simulator. To use these files in GpsGate, select 'Simulator' and then - "File->Open". + "File->Open". diff --git a/xmldoc/formats/gpx.xml b/xmldoc/formats/gpx.xml index e1fba6f6e..e4a37d3a6 100644 --- a/xmldoc/formats/gpx.xml +++ b/xmldoc/formats/gpx.xml @@ -1,15 +1,14 @@ This is one of the most capable and expressive formats of all the file -formats supported by GPSBabel. It is described at topografix.com and is +formats supported by GPSBabel. It is described at topografix.com and is supported by EasyGPS, ExpertGPS, and many other programs described at -topografix.com +topografix.com GPSBabel's reader of this module attempts to preserve tags it doesn't really understand. It also tries to glean interesting data from: - pocket queries from Geocaching.com, + pocket queries from Geocaching.com, Garmin's "gpxx" GPX extensions, Humminbird's "h" GPX extensions. - diff --git a/xmldoc/formats/gtm.xml b/xmldoc/formats/gtm.xml index 8b28f36e4..097e1733e 100644 --- a/xmldoc/formats/gtm.xml +++ b/xmldoc/formats/gtm.xml @@ -1,5 +1,4 @@ Input and output support for waypoints, tracks and routes in - the GPS TrackMaker + the GPS TrackMaker binary format. Code implemented by Gustavo Niemeyer. - diff --git a/xmldoc/formats/gtrnctr.xml b/xmldoc/formats/gtrnctr.xml index 82e0e34b6..8afdcf10d 100644 --- a/xmldoc/formats/gtrnctr.xml +++ b/xmldoc/formats/gtrnctr.xml @@ -1,7 +1,7 @@ GPSBabel supports reading and writing of tracks in the .tcx -format used by Garmin Training Center (GTC). GTC is the successor -to Garmin's Logbook program for their workout units. It is a +format used by Garmin Training Center (GTC). GTC is the successor +to Garmin's Logbook program for their workout units. It is a free upgrade. diff --git a/xmldoc/formats/holux.xml b/xmldoc/formats/holux.xml index 144712199..1af3b3264 100644 --- a/xmldoc/formats/holux.xml +++ b/xmldoc/formats/holux.xml @@ -3,14 +3,14 @@ The Holux gm-100 (e-fox) gps receiver uses standard compact flash cards. File formats were provided by Holux-Taiwan -holux.com to the author. +holux.com to the author. The code was tested against version 2.27E1; other versions and receivers may work but have not been explicitly tested. Anyone with information on other Holux receivers is encouraged to contact jochen@bauerbahn.net. When copying the .wpo file to a flash card, the file must -be named tempwprt.wpo as the +be named tempwprt.wpo as the receiver will ignore all other files. Comparing the waypoints of a .wpo files against other @@ -25,4 +25,3 @@ version 1.14. This program is free of charge from the Holux web site. This format was contributed by Jochen Becker. - diff --git a/xmldoc/formats/html.xml b/xmldoc/formats/html.xml index c99e025ec..606d018cb 100644 --- a/xmldoc/formats/html.xml +++ b/xmldoc/formats/html.xml @@ -18,4 +18,3 @@ gpsbabel -i gpx -f 12345.gpx -o html,stylesheet=green.css,encrypt -F 12345.html - diff --git a/xmldoc/formats/humminbird.xml b/xmldoc/formats/humminbird.xml index 2a8b86d5a..30544f9ac 100644 --- a/xmldoc/formats/humminbird.xml +++ b/xmldoc/formats/humminbird.xml @@ -1,11 +1,11 @@ This format supports: - - Humminbird + + Humminbird waypoints and routes (.hwr files) - Humminbird + Humminbird tracks (.ht files) - Humminbird + Humminbird .dat files. (These accompany the .png files you get when you take snapshots. There are also .dat files generated when making @@ -34,18 +34,17 @@ together with their images. Supported models: - + 797c2i SI (They should all work, but this is the only one tested so far.) Known limits: - + max 12 characters for waypoint names. max 20 characters for route and track names. max 50 points per route. Use simplify filter (count=50 or less) if you have routes with more points! max 21835 points per track. - diff --git a/xmldoc/formats/iblue747.xml b/xmldoc/formats/iblue747.xml index c528b9f1e..4161eecaa 100644 --- a/xmldoc/formats/iblue747.xml +++ b/xmldoc/formats/iblue747.xml @@ -1,5 +1,5 @@ - This is the format used by the software that comes with the Transystem i-Blue747 GPS. + This is the format used by the software that comes with the Transystem i-Blue747 GPS. diff --git a/xmldoc/formats/iblue757.xml b/xmldoc/formats/iblue757.xml index bc3e5f34e..a28e36c0b 100644 --- a/xmldoc/formats/iblue757.xml +++ b/xmldoc/formats/iblue757.xml @@ -1,83 +1,83 @@ This is the format used by the software that comes with the - + Transystem i-Blue757 Pro GPS - . + . It is very similar to the iBlue747 format, apart from the date format being reversed. The csv log file can be extracted from the GPS receiver using - the BT747 software available from + the BT747 software available from http://www.bt747.org Field definitions: -
INDEX +
INDEX A sequential integer which corresponds for each logged point in the file. example 3308
-
RCR +
RCR ? example 1: T example 2: TD
-
DATE +
DATE Date that the point was recorded, in the format YYYY/MM/DD example: 2011/05/14
-
TIME +
TIME Time that the point was recorded, 24-hr format H:MM:SS. Unsure how fractions of a second are handled. example: 4:15:11
-
VALID +
VALID ? example 1: DGPS example 2: SPS
-
LATITUDE +
LATITUDE Degrees above the equator (use negative for south of the equator) example: -33.803645
-
N/S +
N/S North (N)or South (S) of the equator example: S
-
LONGITUDE +
LONGITUDE Degrees east of the Prime Meridian (use negative for east of the Prime Meridian/Greenwich) example: 150.880499
-
E/W +
E/W East (E) or West (W) of Greenwich example: E
-
HEIGHT +
HEIGHT Height above sea level in meters example: 99.859 m
-
SPEED +
SPEED Speed in km/h example: 0.302 km/h
-
DISTANCE +
DISTANCE Distance covered since last point in meters example: 0.30 m
-
Example File +
Example File Example 3.X. Example 'iBlue 757' file diff --git a/xmldoc/formats/igc.xml b/xmldoc/formats/igc.xml index 3e6445c5f..1dfdd070d 100644 --- a/xmldoc/formats/igc.xml +++ b/xmldoc/formats/igc.xml @@ -5,17 +5,17 @@ and from tracks representing recorded flights, and routes representing task declarations in other formats. -
+
IGC Data Format Notes Refer to Appendix 1 of -http://www.fai.org:81/gliding/gnss/tech_spec_gnss.asp +http://www.fai.org:81/gliding/gnss/tech_spec_gnss.asp for the specification of the IGC data format. A sample list of software applications that use data in IGC format can be found at -http://www.fai.org:81/gliding/gnss/gnss_analysis_software.pdf +http://www.fai.org:81/gliding/gnss/gnss_analysis_software.pdf GPSBabel can be used to translate data in IGC format to and from various other @@ -29,7 +29,7 @@ Tracks in other formats are used to represent IGC recorded flights.
-
+
Converting to IGC format IGC files generated by GPSBabel will NOT pass security validation tests since @@ -81,7 +81,7 @@ same file and can be used to fully populate an IGC file: gpsbabel -i gpx -f myall.gpx -o igc -F myflight.igc
-
+
Converting from IGC format Data in an IGC file can be converted into other formats. For example to @@ -104,7 +104,7 @@ tracks. The latitude, longitude and timestamps in the tracks will be identical.
-
+
Merging into IGC format A route stored in another format can be merged with an existing IGC file that @@ -131,4 +131,3 @@ or: (Documentation contributed by Chris Jones, Aug 2004)
- diff --git a/xmldoc/formats/kml.xml b/xmldoc/formats/kml.xml index 585e1f4ba..a824d815c 100644 --- a/xmldoc/formats/kml.xml +++ b/xmldoc/formats/kml.xml @@ -1,6 +1,6 @@ KML, the Keyhole Markup Language format, was used by Keyhole and is used by -Google Earth. +Google Earth. There are concepts in KML that GPSBabel can't support very well on read because they don't map well into other programs. For example, KML has @@ -29,5 +29,5 @@ In general, GPSBabel's KML writer is relatively strong. GPSBabel handles simple you can widen the time slider to show the range of data of interest. - See Google Earth's documentation on timelines for more info. + See Google Earth's documentation on timelines for more info. diff --git a/xmldoc/formats/lowranceusr.xml b/xmldoc/formats/lowranceusr.xml index 1a59b2a64..6bd499e57 100644 --- a/xmldoc/formats/lowranceusr.xml +++ b/xmldoc/formats/lowranceusr.xml @@ -1,17 +1,17 @@ -Many Lowrance systems have the ability +Many Lowrance systems have the ability to output their data to an external storage device. Early models (such as iFinder Hunt) supported an MMC card. Newer models (HDS, Hook, Hook2, etc) support either an SD card or a microSD card. When exported the data is saved to the card as a file. Some models have the ability to export data in GPX format but the -format native to Lowrance units is called USR. +format native to Lowrance units is called USR. Typically the file created by the export operation will have a ".usr" suffix if is a native format or a ".gpx" suffix if is is a GPX format file. -Lowrance units currently use five different versions of USR files. +Lowrance units currently use five different versions of USR files. These different USR versions store the four internal elements (waypoints, routes, trails, and event marker icons) using different formats. Some units do not support all four elements (typically event marker icons are not supported). Some USR formats also have multiple element versions (i.e. USR version 4 has two different formats for storing @@ -22,7 +22,7 @@ five USR formats or even the GPX format. The following provides a high-level description of the multiple USR formats that are supported by the Lowrance product set -(this is based on information contained in the 2018 Lowrance Hook2 Series Operator Manual) and other sources. +(this is based on information contained in the 2018 Lowrance Hook2 Series Operator Manual) and other sources. User Data File version 2 - @@ -83,7 +83,7 @@ The following tables detail the content format of USR data files. Lowrance USR 4, 5 and 6 Trail Object Format - +
Lowrance USR Data File Contents @@ -91,15 +91,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -263,7 +263,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 2 and 3 Waypoint Object Format @@ -271,15 +271,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -375,7 +375,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 4, 5 and 6 Waypoint Object Format @@ -383,15 +383,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -535,7 +535,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 2 and 3 Route Object Format @@ -543,15 +543,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -647,7 +647,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 4, 5 and 6 Route Object Format @@ -655,15 +655,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -748,7 +748,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 4, 5 and 6 Route Leg Object Format @@ -756,15 +756,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -804,7 +804,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 2 and 3 Event Marker ICON Object Format @@ -812,15 +812,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -856,7 +856,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 2 and 3 Trail Object Format @@ -864,15 +864,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -927,7 +927,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 2 and 3 Trail Point Object Format @@ -935,15 +935,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -973,7 +973,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 4, 5 and 6 Trail Object Format @@ -981,15 +981,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -1127,7 +1127,7 @@ The following tables detail the content format of USR data files.
- +
Lowrance USR 4, 5 and 6 Trail Point Object Format @@ -1135,15 +1135,15 @@ The following tables detail the content format of USR data files. - - + + Present In - - - + + + USR 2 @@ -1199,39 +1199,39 @@ The following tables detail the content format of USR data files. Some Lowrance units have the ability to export -GPX (GPS Exchange Format) formatted data. +GPX (GPS Exchange Format) formatted data. Lowrance only provides minimal support for GPX export data on their HOOK2 series (only data available to the author). Refer to -the official GPX 1.1 Schema Documentation for the complete schema. +the official GPX 1.1 Schema Documentation for the complete schema. - + Lowrance GPX Export Data - <metadata> - <time>xsd:dateTime</time> - <depthunits>meters</depthunits> - <tempunits>C</tempunits> - <sogunits>m/s</sogunits> - </metadata> - <wpt lon="longitudeType" lat="latitudeType"> - <time>xsd:dateTime</time> - <name>xsd:string</name> - <sym>xsd:string</sym> - </rte> - <name>xsd:string</name> - <rtept lon="longitudeType" lat="latitudeType"> - <time>xsd:dateTime</time> - <name>xsd:string</name> - <sym>xsd:string</sym> - </rtept> - </rte> - <trk> - <name>xsd:string</name> - <trkseg> - <trkpt lon="longitudeType" lat="latitudeType"> - <time>xsd:dateTime</time> - </trkpt> - </trkseg> - </trk> + <metadata> + <time>xsd:dateTime</time> + <depthunits>meters</depthunits> + <tempunits>C</tempunits> + <sogunits>m/s</sogunits> + </metadata> + <wpt lon="longitudeType" lat="latitudeType"> + <time>xsd:dateTime</time> + <name>xsd:string</name> + <sym>xsd:string</sym> + </rte> + <name>xsd:string</name> + <rtept lon="longitudeType" lat="latitudeType"> + <time>xsd:dateTime</time> + <name>xsd:string</name> + <sym>xsd:string</sym> + </rtept> + </rte> + <trk> + <name>xsd:string</name> + <trkseg> + <trkpt lon="longitudeType" lat="latitudeType"> + <time>xsd:dateTime</time> + </trkpt> + </trkseg> + </trk> diff --git a/xmldoc/formats/m241-bin.xml b/xmldoc/formats/m241-bin.xml index 108f86d69..100d65775 100644 --- a/xmldoc/formats/m241-bin.xml +++ b/xmldoc/formats/m241-bin.xml @@ -4,7 +4,7 @@ configuration, it can store ~100000 trackpoints with very limited data; to configure extended logging you can use the BT747 open source software - bt747 + bt747 Waypoint storage is possible only if "recording reason" (RCR) is enabled in the settings. diff --git a/xmldoc/formats/m241.xml b/xmldoc/formats/m241.xml index fa6602256..182699b31 100644 --- a/xmldoc/formats/m241.xml +++ b/xmldoc/formats/m241.xml @@ -4,7 +4,7 @@ configuration, it can store ~100000 trackpoints with very limited data; to configure extended logging you can use the BT747 open source software - bt747 + bt747 Waypoint storage is possible only if "recording reason" (RCR) is enabled in the settings. @@ -12,7 +12,7 @@ internally used the Silicon Labs CP210X chipset to transform the internal and inaccessible serial port to the USB port that was familiar on the side. The drivers for that port can be found with - SiLabs CP210x serial port drivers. The red and white one existed + SiLabs CP210x serial port drivers. The red and white one existed very briefly before Holux went out of business. GPSBabel does not work with the red and white one. diff --git a/xmldoc/formats/magellan.xml b/xmldoc/formats/magellan.xml index 1c5a47005..9a25f8e6a 100644 --- a/xmldoc/formats/magellan.xml +++ b/xmldoc/formats/magellan.xml @@ -1,5 +1,5 @@ -GPSBabel supports the following Magellan receivers: - +GPSBabel supports the following Magellan receivers: + 310 315 Map330 diff --git a/xmldoc/formats/magellan1.xml b/xmldoc/formats/magellan1.xml index 331bec64d..e3936649a 100644 --- a/xmldoc/formats/magellan1.xml +++ b/xmldoc/formats/magellan1.xml @@ -1,5 +1,5 @@ -GPSBabel supports the following Magellan receivers: - +GPSBabel supports the following Magellan receivers: + 310 315 Map330 @@ -48,7 +48,7 @@ The RoadMate family of products is not supported. This module does not support the units that do not follow Magellan's documented communications protocols including: - + Maestro 3100 Maestro 3140 Maestro 3200 diff --git a/xmldoc/formats/magellanx.xml b/xmldoc/formats/magellanx.xml index 179a7f3c5..ff0742048 100644 --- a/xmldoc/formats/magellanx.xml +++ b/xmldoc/formats/magellanx.xml @@ -1,5 +1,5 @@ - This is the SD card format used by the Magellan Explorist 400, + This is the SD card format used by the Magellan Explorist 400, Explorist 500, Explorist 600, and Explorist XL and internally on those devices plus the Explorist 210. Stored waypoints are identical to the Magellan SD format used by Meridian, but the newer models allow longer waypoint names. Routes are @@ -11,4 +11,3 @@ Similarly, routes should be named ".rte" and tracks should be named ".log". - diff --git a/xmldoc/formats/miniHomer.xml b/xmldoc/formats/miniHomer.xml index 38d25e0fc..fabc1edf2 100644 --- a/xmldoc/formats/miniHomer.xml +++ b/xmldoc/formats/miniHomer.xml @@ -9,7 +9,7 @@ Following a list of devices which should be supported by this module (Note that not all of them have actually been tested, so if you can confirm that additional models work, please mail the gpsbabel-misc group with your success, tips, and any pertinent links for your model.) -
+
Devices supported by miniHomer module @@ -23,8 +23,8 @@ Following a list of devices which should be supported by this module - Navin - Z:NEX + Navin + Z:NEX miniHomer up to 230400 @@ -34,12 +34,12 @@ Following a list of devices which should be supported by this module
- + Command showing miniHomer download of tracks and erasing the logger on Linux gpsbabel -i miniHomer,erase -f /dev/ttyUSB0 -o gpx -F out.gpx - + Command showing miniHomer erasing the logger without download on Linux gpsbabel -i miniHomer,erase,no-output -f /dev/ttyUSB0 @@ -49,7 +49,7 @@ Following a list of devices which should be supported by this module <name>=<lat>:<lng>[:<alt>] Once the according POI symbol is selected on miniHomer, the display shows you the direction and distance to the POI. - + Command showing miniHomer setting Car and Home POI diff --git a/xmldoc/formats/mtk-bin.xml b/xmldoc/formats/mtk-bin.xml index 9a186eba7..85069efbf 100644 --- a/xmldoc/formats/mtk-bin.xml +++ b/xmldoc/formats/mtk-bin.xml @@ -3,7 +3,7 @@ This format reads the raw binary format created by the MTK Windows application and outputs to other formats supported by GPSBabel When using the csv option a MTK application compatible output file will also be created. -It has been tested with Transystem i-Blue 747 but other devices should +It has been tested with Transystem i-Blue 747 but other devices should work as well (Qstarz BT-Q1000, iTrek Z1, ...) All position items (including button push) will be listed as trackpoints in the output. @@ -13,9 +13,9 @@ log session from the button press we would loose a trackpoint unless we include/ -Transystem i-Blue 747 +Transystem i-Blue 747 - + Convert MTK binary trackpoints to GPX gpsbabel -t -i mtk-bin,csv=extra.csv -f data.bin -o gpx -F out.gpx @@ -23,4 +23,3 @@ log session from the button press we would loose a trackpoint unless we include/ - diff --git a/xmldoc/formats/mtk.xml b/xmldoc/formats/mtk.xml index 3543f3b58..49f6848f4 100644 --- a/xmldoc/formats/mtk.xml +++ b/xmldoc/formats/mtk.xml @@ -25,7 +25,7 @@ compass or motion sensors or charging cables with different model numbers. If you can confirm success with others, please share with us. - +
Devices supported by MTK module @@ -39,22 +39,22 @@ If you can confirm success with others, please share with us. iBlue 821 Yes - Available from Semsons + Available from Semsons iBlue 747, 747A+ Yes - Available from Semsons + Available from Semsons QStarz BT-1000, BT-Q1000X, BT-1000eX Yes - + iTrek Z1 - - + + @@ -66,7 +66,7 @@ If you can confirm success with others, please share with us. these devices typically look like Prolific, FTDI, or Silab usb/serial devices to the host OS. You'll need drivers for that whatever chip your product uses for your operating system. For the "A+ GPS Recorder", - the Silicon Labs CP210x chip is used. On OS/X, you'll get + the Silicon Labs CP210x chip is used. On OS/X, you'll get awesome device names like /dev/cu.usbmodem1d13410 - fortunately, our GUI makes that multiple choice so you don't have to guess. @@ -79,17 +79,17 @@ If you can confirm success with others, please share with us. See mtk-bin on how trackpoints/waypoints are handled - + Command showing MTK download track and waypoints and erase on Linux gpsbabel -t -w -i mtk,erase -f /dev/ttyUSB0 -o gpx -F out.gpx For more info and tweaks on MTK based loggers: - MTK Tips and Tweaks and - iBlue 747 Logger + MTK Tips and Tweaks and + iBlue 747 Logger For info about the used log format, see - MTK binary format + MTK binary format Most of the loggers cannot receive bluetooth commands; they can only send diff --git a/xmldoc/formats/navilink.xml b/xmldoc/formats/navilink.xml index 19cf549ed..333ec5a5b 100644 --- a/xmldoc/formats/navilink.xml +++ b/xmldoc/formats/navilink.xml @@ -1,10 +1,10 @@ GPSBabel supports the Navilink protocol used by the - Locosys GT-11 + Locosys GT-11 and - GT-31 + GT-31 GPS receivers. These are sold under a variety of names including: - + NaviGPS NaviGPS-BT GT-11 @@ -33,11 +33,11 @@ present itself to the host operating system. You thus need USB drivers for the PL2303, such as those from the 'Download' section of - + Locosys USB Genie GT-31/BGT-31 drivers - . + . Details of the Navilink serial protocol can be found - here. + here. diff --git a/xmldoc/formats/nmea.xml b/xmldoc/formats/nmea.xml index eb4fb6ecb..6724a93ca 100644 --- a/xmldoc/formats/nmea.xml +++ b/xmldoc/formats/nmea.xml @@ -5,33 +5,33 @@ log and waypoint format for GPS devices. Some hardware and software that work with NMEA-0183 formatted data include: - + - GPS Data Logger + GPS Data Logger - GPS TrackMaker + GPS TrackMaker - GPSMaster + GPSMaster - NMEAlog + NMEAlog - VisualGPS + VisualGPS - GPS Utility + GPS Utility - GeoConv + GeoConv - CommLinx GPS recorder + CommLinx GPS recorder - SparkFun GPS Datalogger + SparkFun GPS Datalogger AMOD 3080 GPS diff --git a/xmldoc/formats/openoffice.xml b/xmldoc/formats/openoffice.xml index 58424f011..415a07c11 100644 --- a/xmldoc/formats/openoffice.xml +++ b/xmldoc/formats/openoffice.xml @@ -3,7 +3,7 @@ format. Intended to serve as source for number-processing applications like OpenOffice, Ploticus and others. Tab was chosen as delimiter because it is a) supported by both OpenOffice and Ploticus - and b) is not ',', so you can use sed -i + and b) is not ',', so you can use sed -i "s/./,/g" <x>.csv' to adapt it to locales where ',' is used as decimal separator. Contributed by Tobias Minich. diff --git a/xmldoc/formats/options/exif-filename.xml b/xmldoc/formats/options/exif-filename.xml index 58f90f2bb..78dd15ac0 100644 --- a/xmldoc/formats/options/exif-filename.xml +++ b/xmldoc/formats/options/exif-filename.xml @@ -7,4 +7,3 @@ The resulting waypoint in OUT.GPX has name IMG_1199. - diff --git a/xmldoc/formats/options/exif-name.xml b/xmldoc/formats/options/exif-name.xml index 0ad934ef9..ff1bbf138 100644 --- a/xmldoc/formats/options/exif-name.xml +++ b/xmldoc/formats/options/exif-name.xml @@ -6,4 +6,3 @@ gpsbabel -i gpx -f holiday.gpx -o exif,name="On the beach" -F IMG0786.JPG - diff --git a/xmldoc/formats/options/garmin-bitscategory.xml b/xmldoc/formats/options/garmin-bitscategory.xml index ee39c4bba..aaa1d97af 100644 --- a/xmldoc/formats/options/garmin-bitscategory.xml +++ b/xmldoc/formats/options/garmin-bitscategory.xml @@ -4,7 +4,7 @@ this options allows you to specify a bitmask to be used for the category. Options may be specified in either decimal or hex. - + Example for garmin bitcategory option to put all waypoints in categories 1 and 16. The following two commands are equivalent. They place a the point in both the first and last of the sixteen available categories. diff --git a/xmldoc/formats/options/garmin-deficon.xml b/xmldoc/formats/options/garmin-deficon.xml index 26ff03d89..01f1ed279 100644 --- a/xmldoc/formats/options/garmin-deficon.xml +++ b/xmldoc/formats/options/garmin-deficon.xml @@ -9,9 +9,8 @@ overrides any icon description that might be in the input file. Value specified may be a number from the Garmin Protocol Spec or a name -as described in the . +as described in the . This option has no effect on input. - diff --git a/xmldoc/formats/options/garmin_gpi-alerts.xml b/xmldoc/formats/options/garmin_gpi-alerts.xml index 7962fac85..06ea391a7 100644 --- a/xmldoc/formats/options/garmin_gpi-alerts.xml +++ b/xmldoc/formats/options/garmin_gpi-alerts.xml @@ -12,4 +12,3 @@ gpsbabel -i gpx -f "warnings.gpx" -o garmin_gpi,alerts=1 -F "warnings.gpi" - diff --git a/xmldoc/formats/options/garmin_gpi-languagecode.xml b/xmldoc/formats/options/garmin_gpi-languagecode.xml index fb1217108..68d84616f 100644 --- a/xmldoc/formats/options/garmin_gpi-languagecode.xml +++ b/xmldoc/formats/options/garmin_gpi-languagecode.xml @@ -5,7 +5,7 @@ to use GPSBabel will print an error message containing the language codes used i Subsequently you may use one of these codes with the languagecode option to specify which language to use. - + Example with unspecified language and a garmin points of interest dual language file. @@ -17,7 +17,7 @@ option to specify which language to use. - + Example for specifying language with a garmin points of interest dual language file. diff --git a/xmldoc/formats/options/garmin_gpi-notes.xml b/xmldoc/formats/options/garmin_gpi-notes.xml index c9d5382b6..0c3f451e1 100644 --- a/xmldoc/formats/options/garmin_gpi-notes.xml +++ b/xmldoc/formats/options/garmin_gpi-notes.xml @@ -8,4 +8,3 @@ gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,notes -F "My Points.gpi" - diff --git a/xmldoc/formats/options/garmin_gpi-proximity.xml b/xmldoc/formats/options/garmin_gpi-proximity.xml index cba909bef..9760102fc 100644 --- a/xmldoc/formats/options/garmin_gpi-proximity.xml +++ b/xmldoc/formats/options/garmin_gpi-proximity.xml @@ -3,7 +3,7 @@ The parameter has to be in meters, or, when units=s specified, in miles. alerts are automatically enabled. - + Read GPX file, create GPI to alert when you're 1/2 mile from a speed camera. @@ -20,7 +20,7 @@ -
+
Supported distance units (garmin_gpi) diff --git a/xmldoc/formats/options/garmin_gpi-speed.xml b/xmldoc/formats/options/garmin_gpi-speed.xml index 0c8123958..37ee04b7f 100644 --- a/xmldoc/formats/options/garmin_gpi-speed.xml +++ b/xmldoc/formats/options/garmin_gpi-speed.xml @@ -18,7 +18,7 @@ -
+
Supported speed units (garmin_gpi) diff --git a/xmldoc/formats/options/garmin_gpi-unique.xml b/xmldoc/formats/options/garmin_gpi-unique.xml index 3985fa9c2..9af12b0e0 100644 --- a/xmldoc/formats/options/garmin_gpi-unique.xml +++ b/xmldoc/formats/options/garmin_gpi-unique.xml @@ -6,4 +6,3 @@ gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,unique=0 -F "My Points.gpi" - diff --git a/xmldoc/formats/options/garmin_gpi-units.xml b/xmldoc/formats/options/garmin_gpi-units.xml index fc344b750..466697f1f 100644 --- a/xmldoc/formats/options/garmin_gpi-units.xml +++ b/xmldoc/formats/options/garmin_gpi-units.xml @@ -4,4 +4,3 @@ gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,units=s -F "My Points.gpi" - diff --git a/xmldoc/formats/options/garmin_txt-datum.xml b/xmldoc/formats/options/garmin_txt-datum.xml index b5c8a5a06..e3c0d104f 100644 --- a/xmldoc/formats/options/garmin_txt-datum.xml +++ b/xmldoc/formats/options/garmin_txt-datum.xml @@ -1,4 +1,4 @@ This option specifies the datum to be used on output. Valid values for this -option are listed in . +option are listed in . diff --git a/xmldoc/formats/options/garmin_txt-grid.xml b/xmldoc/formats/options/garmin_txt-grid.xml index 70365d0a4..78da4e2b1 100644 --- a/xmldoc/formats/options/garmin_txt-grid.xml +++ b/xmldoc/formats/options/garmin_txt-grid.xml @@ -1,7 +1,7 @@ This value specifies the grid to be used on write. -
+
Grid values for garmin_txt @@ -58,5 +58,3 @@ Idx or short are valid params for this option. - - diff --git a/xmldoc/formats/options/gdb-bitscategory.xml b/xmldoc/formats/options/gdb-bitscategory.xml index a38778130..4a08e86b6 100644 --- a/xmldoc/formats/options/gdb-bitscategory.xml +++ b/xmldoc/formats/options/gdb-bitscategory.xml @@ -4,7 +4,7 @@ this options allows you to specify a bitmask to be used for the category. Options may be specified in either decimal or hex. - + Example for gdb bitcategory option to put all waypoints in categories 1 and 16. The following two commands are equivalent. They place a the point in both the first and last of the sixteen available categories. diff --git a/xmldoc/formats/options/gdb-dropwpt.xml b/xmldoc/formats/options/gdb-dropwpt.xml index 8a56051a1..baa3b0ff8 100644 --- a/xmldoc/formats/options/gdb-dropwpt.xml +++ b/xmldoc/formats/options/gdb-dropwpt.xml @@ -2,4 +2,3 @@ This option instructs GPSBabel to drop hidden (calculated) points from routes when creating waypoints. These points are not converted to waypoints, but they are converted to route points. - diff --git a/xmldoc/formats/options/gdb-roadbook.xml b/xmldoc/formats/options/gdb-roadbook.xml index c17af7243..5080dd0f8 100644 --- a/xmldoc/formats/options/gdb-roadbook.xml +++ b/xmldoc/formats/options/gdb-roadbook.xml @@ -4,7 +4,7 @@ The priority of this option is higher than of the and options. A value of 1 or y overwrites the and settings. - + Using gdb option <option>roadbook</option> to create simple html roadbook diff --git a/xmldoc/formats/options/gdb-via.xml b/xmldoc/formats/options/gdb-via.xml index 439d675f9..7549ab510 100644 --- a/xmldoc/formats/options/gdb-via.xml +++ b/xmldoc/formats/options/gdb-via.xml @@ -2,4 +2,3 @@ This option instructs GPSBabel to drop hidden (calculated) points from routes. These points are not converted to waypoints or route points. - diff --git a/xmldoc/formats/options/geo-deficon.xml b/xmldoc/formats/options/geo-deficon.xml index bef014fd1..02efe2b57 100644 --- a/xmldoc/formats/options/geo-deficon.xml +++ b/xmldoc/formats/options/geo-deficon.xml @@ -13,5 +13,3 @@ There is no list of valid values for this option. This option has no effect on input. - - diff --git a/xmldoc/formats/options/geo-nuke_placer.xml b/xmldoc/formats/options/geo-nuke_placer.xml index d9987d249..325861d02 100644 --- a/xmldoc/formats/options/geo-nuke_placer.xml +++ b/xmldoc/formats/options/geo-nuke_placer.xml @@ -6,4 +6,3 @@ input file. This option has no effect on output. - diff --git a/xmldoc/formats/options/globalsat-showlist.xml b/xmldoc/formats/options/globalsat-showlist.xml index de46c5a8c..9a9c7288f 100644 --- a/xmldoc/formats/options/globalsat-showlist.xml +++ b/xmldoc/formats/options/globalsat-showlist.xml @@ -1,7 +1,7 @@ The showlist argument displays the list of tracks stored on the device. - + Command showing list of tracks on device gpsbabel -i globalsat,showlist=1 -f /dev/ttyUSB0 diff --git a/xmldoc/formats/options/globalsat-track.xml b/xmldoc/formats/options/globalsat-track.xml index 42e0ec177..fa0ff87e2 100644 --- a/xmldoc/formats/options/globalsat-track.xml +++ b/xmldoc/formats/options/globalsat-track.xml @@ -3,7 +3,7 @@ The 'track' option is used to fetch a single named track, probably one you learned about via the 'showlist' option from a previous invocation, instead of fetching all the tracks, which is our default. - + Command track can be used to fetch a single track, default is all tracks gpsbabel -i globalsat,track=number -f /dev/ttyUSB0 -o gpx,garminextensions -F outfile.gpx diff --git a/xmldoc/formats/options/gpx-logpoint.xml b/xmldoc/formats/options/gpx-logpoint.xml index 2739b4889..eb4a29713 100644 --- a/xmldoc/formats/options/gpx-logpoint.xml +++ b/xmldoc/formats/options/gpx-logpoint.xml @@ -1,5 +1,5 @@ - When reading Groundspeak Pocket Queries , the option creates additional waypoints from the log entries. + When reading Groundspeak Pocket Queries , the option creates additional waypoints from the log entries. A typical use for this is to get coordinates read from "corrected coordinates" logs. diff --git a/xmldoc/formats/options/gpx-urlbase.xml b/xmldoc/formats/options/gpx-urlbase.xml index fefa663cf..4f3169dea 100644 --- a/xmldoc/formats/options/gpx-urlbase.xml +++ b/xmldoc/formats/options/gpx-urlbase.xml @@ -1,4 +1,3 @@ This is a fairly esoteric option. If the GPX file you are reading has only base pathnames (e.g "foo.html") the value you specify to this argument will be prepended to that. For example, "-o gpx,urlbase=c:\My Documents\Whatever" would result in the link to that waypoint being written to refer to c:\My Document\WHatever\foo.html - diff --git a/xmldoc/formats/options/igc-timeadj.xml b/xmldoc/formats/options/igc-timeadj.xml index eb345d9b8..e64003055 100644 --- a/xmldoc/formats/options/igc-timeadj.xml +++ b/xmldoc/formats/options/igc-timeadj.xml @@ -12,5 +12,3 @@ is done by comparing the time that it thinks that you landed on the GPS track and the barograph and adjusting accordingly: gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc - - diff --git a/xmldoc/formats/options/kml-line_color.xml b/xmldoc/formats/options/kml-line_color.xml index 3bbc62cfe..da776a159 100644 --- a/xmldoc/formats/options/kml-line_color.xml +++ b/xmldoc/formats/options/kml-line_color.xml @@ -2,4 +2,3 @@ This option specifies the line color as a hexadecimal number in AABBGGRR format, where A is alpha, B is blue, G is green, and R is red. - diff --git a/xmldoc/formats/options/kml-points.xml b/xmldoc/formats/options/kml-points.xml index 3f8241d46..547b28deb 100644 --- a/xmldoc/formats/options/kml-points.xml +++ b/xmldoc/formats/options/kml-points.xml @@ -3,4 +3,3 @@ When this option is nonzero, GPSBabel draws placemarks for tracks and routes. The default value for this option is 1, which causes placemarks to be drawn. To disable drawing of placemarks, specify . - diff --git a/xmldoc/formats/options/m241-erase.xml b/xmldoc/formats/options/m241-erase.xml index fa36635ae..95424f0dd 100644 --- a/xmldoc/formats/options/m241-erase.xml +++ b/xmldoc/formats/options/m241-erase.xml @@ -1,2 +1 @@ This option erases the track log from the device after download. - diff --git a/xmldoc/formats/options/miniHomer-Bar.xml b/xmldoc/formats/options/miniHomer-Bar.xml index 6eb54e27b..cb78929d4 100644 --- a/xmldoc/formats/options/miniHomer-Bar.xml +++ b/xmldoc/formats/options/miniHomer-Bar.xml @@ -6,7 +6,7 @@ You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. - + Set the target location of the miniHomer Bar POI gpsbabel -i miniHomer,Bar=38.99809:-86.34662 -f /dev/ttyUSB0 -o unicsv -F - @@ -17,4 +17,3 @@ this location as soon as it has a satellite fix. - diff --git a/xmldoc/formats/options/miniHomer-Boat.xml b/xmldoc/formats/options/miniHomer-Boat.xml index 9d26fb393..763a42b69 100644 --- a/xmldoc/formats/options/miniHomer-Boat.xml +++ b/xmldoc/formats/options/miniHomer-Boat.xml @@ -6,7 +6,7 @@ You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. - + Set the target location of the miniHomer Boat POI gpsbabel -i miniHomer,Boat=32.29287:-64.77527 -f /dev/ttyUSB0 -o unicsv -F - @@ -17,4 +17,3 @@ this location as soon as it has a satellite fix. - diff --git a/xmldoc/formats/options/miniHomer-Car.xml b/xmldoc/formats/options/miniHomer-Car.xml index 38690b9e4..f1a497c90 100644 --- a/xmldoc/formats/options/miniHomer-Car.xml +++ b/xmldoc/formats/options/miniHomer-Car.xml @@ -6,7 +6,7 @@ You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. - + Set the target location of the miniHomer Car POI gpsbabel -i miniHomer,Car=-25.272309:153.235330 -f /dev/ttyUSB0 -o unicsv -F - @@ -17,4 +17,3 @@ this location as soon as it has a satellite fix. - diff --git a/xmldoc/formats/options/miniHomer-Heart.xml b/xmldoc/formats/options/miniHomer-Heart.xml index 3c07af1da..d55c31aa1 100644 --- a/xmldoc/formats/options/miniHomer-Heart.xml +++ b/xmldoc/formats/options/miniHomer-Heart.xml @@ -6,7 +6,7 @@ You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. - + Set the target location of the miniHomer Heart POI gpsbabel -i miniHomer,Heart=36.1269:-115.1698 -f /dev/ttyUSB0 -o unicsv -F - @@ -17,4 +17,3 @@ this location as soon as it has a satellite fix. - diff --git a/xmldoc/formats/options/miniHomer-Home.xml b/xmldoc/formats/options/miniHomer-Home.xml index c583063b8..53e304a10 100644 --- a/xmldoc/formats/options/miniHomer-Home.xml +++ b/xmldoc/formats/options/miniHomer-Home.xml @@ -6,7 +6,7 @@ You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. - + Set the target location of the miniHomer Home POI gpsbabel -i miniHomer,Home=-3.066667:37.359167:5895 -f /dev/ttyUSB0 -o unicsv -F - @@ -17,4 +17,3 @@ this location as soon as it has a satellite fix. - diff --git a/xmldoc/formats/options/miniHomer-erase.xml b/xmldoc/formats/options/miniHomer-erase.xml index 7921eb515..d6db3d8e7 100644 --- a/xmldoc/formats/options/miniHomer-erase.xml +++ b/xmldoc/formats/options/miniHomer-erase.xml @@ -1,4 +1,3 @@ Erase log buffer. - diff --git a/xmldoc/formats/options/miniHomer-first-sector.xml b/xmldoc/formats/options/miniHomer-first-sector.xml index 1802768cf..d100b4c10 100644 --- a/xmldoc/formats/options/miniHomer-first-sector.xml +++ b/xmldoc/formats/options/miniHomer-first-sector.xml @@ -9,7 +9,7 @@ erased again by the user. that on erase, only the first two sectors are actually cleared. The following example shows how to read the remaining data: - + Command showing how to read data from an erased device gpsbabel -i miniHomer,first-sector=2 -f /dev/ttyUSB0 -o gpx -F out.gpx diff --git a/xmldoc/formats/options/miniHomer-initbaud.xml b/xmldoc/formats/options/miniHomer-initbaud.xml index 5b99e8e35..9b7c3f8d2 100644 --- a/xmldoc/formats/options/miniHomer-initbaud.xml +++ b/xmldoc/formats/options/miniHomer-initbaud.xml @@ -10,4 +10,3 @@ rate, if initbaud wasn't given), the initial setting will be restored after fini Please note that miniHomer by default uses 38400bps and does not autodetect the port speed. If you need autodetect, start as gpsbabel -i miniHomer,initbaud=0 -f /dev/ttyUSB0 -o gpx -F out.gpx - diff --git a/xmldoc/formats/options/miniHomer-read-at-once.xml b/xmldoc/formats/options/miniHomer-read-at-once.xml index 7283235cb..91700ecd7 100644 --- a/xmldoc/formats/options/miniHomer-read-at-once.xml +++ b/xmldoc/formats/options/miniHomer-read-at-once.xml @@ -1,4 +1,4 @@ -If read-at-once >= 1, batch mode is enabled with that many sectors being read at a time. +If read-at-once >= 1, batch mode is enabled with that many sectors being read at a time. A value of zero disables batch mode and switches to single read mode. Not all devices support batch mode; in that case gpsbabel automatically switches to single read mode. diff --git a/xmldoc/formats/options/nmea-date.xml b/xmldoc/formats/options/nmea-date.xml index e007e5a03..cdec33e49 100644 --- a/xmldoc/formats/options/nmea-date.xml +++ b/xmldoc/formats/options/nmea-date.xml @@ -6,5 +6,3 @@ This is necessary because some NMEA sentences contain times but no dates. If this option is not specified and the date cannot be determined from one or more of the available NMEA sentences, the tracks will be discarded. - - diff --git a/xmldoc/formats/options/nmea-gisteq.xml b/xmldoc/formats/options/nmea-gisteq.xml index d1e450265..fccea3a9b 100644 --- a/xmldoc/formats/options/nmea-gisteq.xml +++ b/xmldoc/formats/options/nmea-gisteq.xml @@ -13,5 +13,5 @@ More information can be found at the -Gisteq site. +Gisteq site. diff --git a/xmldoc/formats/options/nmea-gpgsa.xml b/xmldoc/formats/options/nmea-gpgsa.xml index 277556079..c3b6bae2f 100644 --- a/xmldoc/formats/options/nmea-gpgsa.xml +++ b/xmldoc/formats/options/nmea-gpgsa.xml @@ -9,4 +9,3 @@ and the individual satellites from which it was derived. However, GPSBabel neither reads nor writes the individual satellite data. On input, the satellite fields are ignored and on output they are left blank. - diff --git a/xmldoc/formats/options/nmea-gprmc.xml b/xmldoc/formats/options/nmea-gprmc.xml index 78de6e63c..1b9493bc7 100644 --- a/xmldoc/formats/options/nmea-gprmc.xml +++ b/xmldoc/formats/options/nmea-gprmc.xml @@ -8,4 +8,3 @@ GPRMC sentences contain the "recommended minimum" positional information, including date and time, heading, and velocity. Note that they do not include altitude. For altitude, you will have to include GPGGA sentences. - diff --git a/xmldoc/formats/options/nmea-gpvtg.xml b/xmldoc/formats/options/nmea-gpvtg.xml index 3680b7f20..5b11af291 100644 --- a/xmldoc/formats/options/nmea-gpvtg.xml +++ b/xmldoc/formats/options/nmea-gpvtg.xml @@ -8,4 +8,3 @@ GPVTG sentences contain information about the heading and the speed at the time of the fix. They do not contain any location information; for that you will need either or both of GPGGA or GPRMC. - diff --git a/xmldoc/formats/options/nmea-pause.xml b/xmldoc/formats/options/nmea-pause.xml index 2d805bb15..3a8cdff5a 100644 --- a/xmldoc/formats/options/nmea-pause.xml +++ b/xmldoc/formats/options/nmea-pause.xml @@ -28,4 +28,3 @@ If you are using this option with compressed or simplified tracks from your handheld GPS receiver, you might find the interpolate filter useful. - diff --git a/xmldoc/formats/options/nmea-snlen.xml b/xmldoc/formats/options/nmea-snlen.xml index d14ee7430..87a35f101 100644 --- a/xmldoc/formats/options/nmea-snlen.xml +++ b/xmldoc/formats/options/nmea-snlen.xml @@ -3,4 +3,3 @@ This option specifies the maximum length to be used for waypoint names in the GPWPL sentence. Longer names will be shortened to no more than this length, but all waypoint names will remain unique. - diff --git a/xmldoc/formats/options/osm-tag.xml b/xmldoc/formats/options/osm-tag.xml index 752fa5508..507627a83 100644 --- a/xmldoc/formats/options/osm-tag.xml +++ b/xmldoc/formats/options/osm-tag.xml @@ -1,5 +1,5 @@ - With this option you can preset OSM features (tags) on all exported ways. + With this option you can preset OSM features (tags) on all exported ways. gpsbabel -i gdb -f ways.gdb -o osm,tag="highway:motorway" -F ways.osm diff --git a/xmldoc/formats/options/osm-tagnd.xml b/xmldoc/formats/options/osm-tagnd.xml index f9b10abc9..07cde4799 100644 --- a/xmldoc/formats/options/osm-tagnd.xml +++ b/xmldoc/formats/options/osm-tagnd.xml @@ -1,5 +1,5 @@ - With this option you can preset OSM features (tags) on every written nodes. + With this option you can preset OSM features (tags) on every written nodes. gpsbabel -i gdb -f nodes.gdb -o osm,tagnd="amenity:pub;building:yes" -F nodes.osm diff --git a/xmldoc/formats/options/ozi-altunit.xml b/xmldoc/formats/options/ozi-altunit.xml index 1df78a26f..b927010f4 100644 --- a/xmldoc/formats/options/ozi-altunit.xml +++ b/xmldoc/formats/options/ozi-altunit.xml @@ -2,4 +2,3 @@ By default the ozi module uses feet as altitude unit. With this option you can specify also 'Meters' (m) as unit for altitude values. - diff --git a/xmldoc/formats/options/skytraq-configlog.xml b/xmldoc/formats/options/skytraq-configlog.xml index 6aa23eddd..87e30e3dc 100644 --- a/xmldoc/formats/options/skytraq-configlog.xml +++ b/xmldoc/formats/options/skytraq-configlog.xml @@ -5,7 +5,7 @@ and v the current speed, the device logs if - (dt > tmin and dx >= dmin and v >= vmin) or dt > tmax or dx > dmax or v > vmax + (dt > tmin and dx >= dmin and v >= vmin) or dt > tmax or dx > dmax or v > vmax If you use this option, vmin is fixed at 0 and vmax at 65535 km/h. @@ -15,7 +15,7 @@ happens first!) - + Set the logging parameters for Skytraq device diff --git a/xmldoc/formats/options/skytraq-first-sector.xml b/xmldoc/formats/options/skytraq-first-sector.xml index 770b941f2..2207291cd 100644 --- a/xmldoc/formats/options/skytraq-first-sector.xml +++ b/xmldoc/formats/options/skytraq-first-sector.xml @@ -6,7 +6,7 @@ erased again by the user. that on erase, only the first two sectors are actually cleared. The following example shows how to read the remaining data: - + Command showing how to read data from an erased device gpsbabel -i skytraq,first-sector=2 -f /dev/ttyUSB0 -o gpx -F out.gpx diff --git a/xmldoc/formats/options/skytraq-gps-utc-offset.xml b/xmldoc/formats/options/skytraq-gps-utc-offset.xml index 1eef86a85..5cfb004c0 100644 --- a/xmldoc/formats/options/skytraq-gps-utc-offset.xml +++ b/xmldoc/formats/options/skytraq-gps-utc-offset.xml @@ -14,5 +14,5 @@ Indicates that GPS is ahead of UTC by fifteen seconds, as was the case in 2009. -Consult formal explanation of GPS time vs. UTC time if you're into that. +Consult formal explanation of GPS time vs. UTC time if you're into that. diff --git a/xmldoc/formats/options/skytraq-gps-week-rollover.xml b/xmldoc/formats/options/skytraq-gps-week-rollover.xml index 131445a6b..d3a1651f6 100644 --- a/xmldoc/formats/options/skytraq-gps-week-rollover.xml +++ b/xmldoc/formats/options/skytraq-gps-week-rollover.xml @@ -4,7 +4,7 @@ we're currently in: skytraq log data contains dates in the form of GPS weeks, which roll over to 0 every 1024 weeks (close to 20 years). -
+
GPS week rollover dates diff --git a/xmldoc/formats/options/skytraq-read-at-once.xml b/xmldoc/formats/options/skytraq-read-at-once.xml index 7283235cb..91700ecd7 100644 --- a/xmldoc/formats/options/skytraq-read-at-once.xml +++ b/xmldoc/formats/options/skytraq-read-at-once.xml @@ -1,4 +1,4 @@ -If read-at-once >= 1, batch mode is enabled with that many sectors being read at a time. +If read-at-once >= 1, batch mode is enabled with that many sectors being read at a time. A value of zero disables batch mode and switches to single read mode. Not all devices support batch mode; in that case gpsbabel automatically switches to single read mode. diff --git a/xmldoc/formats/options/skytraq-targetlocation.xml b/xmldoc/formats/options/skytraq-targetlocation.xml index e987dcdeb..db19cbf86 100644 --- a/xmldoc/formats/options/skytraq-targetlocation.xml +++ b/xmldoc/formats/options/skytraq-targetlocation.xml @@ -5,7 +5,7 @@ and longitude. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. - + Set the target location of the Skytraq location finder gpsbabel -i skytraq,targetlocation=12.34:-56.78 -f /dev/ttyUSB @@ -18,4 +18,3 @@ it has a satellite fix. - diff --git a/xmldoc/formats/options/subrip-format.xml b/xmldoc/formats/options/subrip-format.xml index c6f1054e5..c2ba4ca90 100644 --- a/xmldoc/formats/options/subrip-format.xml +++ b/xmldoc/formats/options/subrip-format.xml @@ -1,7 +1,7 @@ Format for output subtitles. -
+
Supported format characters for subrip diff --git a/xmldoc/formats/options/text-splitoutput.xml b/xmldoc/formats/options/text-splitoutput.xml index 6ca7fcd49..041cadd78 100644 --- a/xmldoc/formats/options/text-splitoutput.xml +++ b/xmldoc/formats/options/text-splitoutput.xml @@ -2,7 +2,7 @@ Splits output into separate files for each waypoint by appending a decimal number to the output filename. - + Example for splitoutput option to text format If "MyPQ.gpx" contains five waypoints, diff --git a/xmldoc/formats/options/tpg-datum.xml b/xmldoc/formats/options/tpg-datum.xml index 7a63f31ba..8e5af9afd 100644 --- a/xmldoc/formats/options/tpg-datum.xml +++ b/xmldoc/formats/options/tpg-datum.xml @@ -3,4 +3,3 @@ the default of NAD27 ("N. America 1927 mean") which is correct for the continental U.S. Any legal datum supported by GPSBabel may be used. For example, points in Hawaii should use "Old Hawaiian_mean". - diff --git a/xmldoc/formats/options/unicsv-datum.xml b/xmldoc/formats/options/unicsv-datum.xml index 80b85eae7..2899fbbd3 100644 --- a/xmldoc/formats/options/unicsv-datum.xml +++ b/xmldoc/formats/options/unicsv-datum.xml @@ -1,4 +1,4 @@ This option specifies the datum to be used on output. Valid values for this - option are listed in . + option are listed in . diff --git a/xmldoc/formats/options/unicsv-fields.xml b/xmldoc/formats/options/unicsv-fields.xml index f21492848..73640eb2a 100644 --- a/xmldoc/formats/options/unicsv-fields.xml +++ b/xmldoc/formats/options/unicsv-fields.xml @@ -6,7 +6,7 @@ The list of field names is exactly that allowed in the first line of a unicsv file without this option. - + Example for unicsv fields option to describe input file. For example ... diff --git a/xmldoc/formats/options/unicsv-filename.xml b/xmldoc/formats/options/unicsv-filename.xml index e49c748a2..c5f10649c 100644 --- a/xmldoc/formats/options/unicsv-filename.xml +++ b/xmldoc/formats/options/unicsv-filename.xml @@ -6,7 +6,7 @@ This can be very helpful for locating specific waypoints (i.e. using the position filter) in more than one file. - + Example for unicsv filename option to write filenames of input formats. The next example ... diff --git a/xmldoc/formats/options/unicsv-format.xml b/xmldoc/formats/options/unicsv-format.xml index 58b1916bb..53cc23327 100644 --- a/xmldoc/formats/options/unicsv-format.xml +++ b/xmldoc/formats/options/unicsv-format.xml @@ -2,7 +2,7 @@ When this option is enabled, we generate an additional 'Format' column. The values of this column are filled with names of previous input formats. - + Example for unicsv format option to write names of input formats. The next example ... @@ -19,4 +19,3 @@ - diff --git a/xmldoc/formats/options/unicsv-grid.xml b/xmldoc/formats/options/unicsv-grid.xml index 7d6cab0a4..65f1fff1b 100644 --- a/xmldoc/formats/options/unicsv-grid.xml +++ b/xmldoc/formats/options/unicsv-grid.xml @@ -1,6 +1,6 @@ This value specifies the grid to be used on write. It is similar to - the grid option of garmin_txt (see ). The only difference is that unicsv does not + the grid option of garmin_txt (see ). The only difference is that unicsv does not write a degree sign (°) into the output file. diff --git a/xmldoc/formats/options/vcard-encrypt.xml b/xmldoc/formats/options/vcard-encrypt.xml index 1ba2851e2..7a5eef15a 100644 --- a/xmldoc/formats/options/vcard-encrypt.xml +++ b/xmldoc/formats/options/vcard-encrypt.xml @@ -1,4 +1,3 @@ By default geocaching hints are unencrypted; use this option to encrypt them. - diff --git a/xmldoc/formats/options/xcsv-datum.xml b/xmldoc/formats/options/xcsv-datum.xml index ea17ec5fa..8580cd701 100644 --- a/xmldoc/formats/options/xcsv-datum.xml +++ b/xmldoc/formats/options/xcsv-datum.xml @@ -1,4 +1,4 @@ This option specifies the GPS datum to be used on read or write. Valid values for this -option are listed in . +option are listed in . diff --git a/xmldoc/formats/options/xcsv-snlen.xml b/xmldoc/formats/options/xcsv-snlen.xml index 9318463ce..9a296f683 100644 --- a/xmldoc/formats/options/xcsv-snlen.xml +++ b/xmldoc/formats/options/xcsv-snlen.xml @@ -5,4 +5,3 @@ output. This option overrides the style file. Valid values for this option are 0 (off) and 1 (on). - diff --git a/xmldoc/formats/options/xcsv-snunique.xml b/xmldoc/formats/options/xcsv-snunique.xml index 1687cbec1..746bec42c 100644 --- a/xmldoc/formats/options/xcsv-snunique.xml +++ b/xmldoc/formats/options/xcsv-snunique.xml @@ -5,4 +5,3 @@ unique within the output file. This option overrides the style file. Valid values for this option are 0 (off) and 1 (on). - diff --git a/xmldoc/formats/options/xcsv-snupper.xml b/xmldoc/formats/options/xcsv-snupper.xml index 99400ee91..50c40be0f 100644 --- a/xmldoc/formats/options/xcsv-snupper.xml +++ b/xmldoc/formats/options/xcsv-snupper.xml @@ -5,4 +5,3 @@ only UPPERCASE characters. This option overrides the style file. Valid values for this option are 0 (off) and 1 (on). - diff --git a/xmldoc/formats/options/xcsv-style.xml b/xmldoc/formats/options/xcsv-style.xml index 815467fbb..02c90283c 100644 --- a/xmldoc/formats/options/xcsv-style.xml +++ b/xmldoc/formats/options/xcsv-style.xml @@ -5,6 +5,5 @@ built-in xcsv-based styles; they have prebuilt style definitions. For information on the format of xcsv style files, see -. +. - diff --git a/xmldoc/formats/osm.xml b/xmldoc/formats/osm.xml index 0dc4d3bf3..08bb6dfa0 100644 --- a/xmldoc/formats/osm.xml +++ b/xmldoc/formats/osm.xml @@ -1,11 +1,11 @@ - This format is used to exchange data with the OpenStreetMap project. + This format is used to exchange data with the OpenStreetMap project. The main goal of this collaborative project is to create free editable maps. These data files are XML based. Every GPS element (way or node) described by the files has a unique number as identifier. When we write OSM data files and don't know something about the id's, - negative numbers will be used as identifier. This has been tested with JOSM. + negative numbers will be used as identifier. This has been tested with JOSM. Because the resulting timestamps of OSM ways differ from real GPS tracks, diff --git a/xmldoc/formats/sbn.xml b/xmldoc/formats/sbn.xml index 7adb91fd4..d748112d6 100644 --- a/xmldoc/formats/sbn.xml +++ b/xmldoc/formats/sbn.xml @@ -10,7 +10,7 @@ Not all data logged in this format is converted by GPSBabel, but the following are: - + Position Elevation Time @@ -24,7 +24,7 @@ The specification of this format can be found in - the - SiRF Binary Protocol Reference Manual, in the section + the + SiRF Binary Protocol Reference Manual, in the section called Geodetic Navigation Data - Message ID 41. diff --git a/xmldoc/formats/skytraq.xml b/xmldoc/formats/skytraq.xml index 6c9d90260..2e828b40c 100644 --- a/xmldoc/formats/skytraq.xml +++ b/xmldoc/formats/skytraq.xml @@ -6,7 +6,7 @@ use this format to read its memory. Following a list of devices which should be supported by this module (Note that not all of them have actually been tested, so if you can confirm that additional models work, please mail the gpsbabel-misc group with your success, tips, and any pertinent links for your model.): -
+
Devices supported by skytraq module @@ -77,12 +77,12 @@ use this format to read its memory.
Windows users of GPSBabel version 1.5.2 or less may have to explicitly specifiy a bit rate of 115200 or lower. - + Command showing skytraq download of tracks and erasing the logger on Linux gpsbabel -i skytraq,erase -f /dev/ttyUSB0 -o gpx -F out.gpx - + Command showing skytraq erasing the logger without download on Linux gpsbabel -i skytraq,erase,no-output -f /dev/ttyUSB0 @@ -90,7 +90,7 @@ use this format to read its memory. If available, reading the logger using bluetooth should also work. However, many devices support only one specific baud rate over bluetooth, e.g. 9600. In that case you should use the option baud=0 to tell GPSBabel to use that default baud rate: - + Command showing skytraq download tracks via bluetooth on Linux rfcomm bind 0 <bdaddr> gpsbabel -i skytraq,baud=0 -f /dev/rfcomm0 -o gpx -F out.gpx diff --git a/xmldoc/formats/tabsep.xml b/xmldoc/formats/tabsep.xml index 886d318e9..19929c7f7 100644 --- a/xmldoc/formats/tabsep.xml +++ b/xmldoc/formats/tabsep.xml @@ -3,10 +3,9 @@ This format, like the custom format, is mainly used for the purpose of testing GPSBabel. It is supposed to contain one field for each piece of information supported by the xcsv format writer, but it may not be entirely -in sync with the documentation at . +in sync with the documentation at . For a list of fields, see the style/tabsep.style file in the GPSBabel source distribution. - diff --git a/xmldoc/formats/text.xml b/xmldoc/formats/text.xml index c429b2493..e31adbe6d 100644 --- a/xmldoc/formats/text.xml +++ b/xmldoc/formats/text.xml @@ -5,4 +5,3 @@ handy for listings of any type of waypoint files. Groundspeak extensions and writes a text file with encrypted hints: gpsbabel -i gpx -f 12345.gpx -o text,encrypt -F 12345.txt - diff --git a/xmldoc/formats/tpg.xml b/xmldoc/formats/tpg.xml index 71e37f3ad..f5447e297 100644 --- a/xmldoc/formats/tpg.xml +++ b/xmldoc/formats/tpg.xml @@ -5,4 +5,3 @@ reads and writes .TPG files created by various editions of NG Topo! Reading/writing of route data is not supported yet. Contributed by Alex Mottram. - diff --git a/xmldoc/formats/tpo2.xml b/xmldoc/formats/tpo2.xml index 237d8c077..d3dfb765b 100644 --- a/xmldoc/formats/tpo2.xml +++ b/xmldoc/formats/tpo2.xml @@ -5,5 +5,3 @@ Contributed by Steve Chamberlin. - - diff --git a/xmldoc/formats/tpo3.xml b/xmldoc/formats/tpo3.xml index ce5d0ff40..20274eb72 100644 --- a/xmldoc/formats/tpo3.xml +++ b/xmldoc/formats/tpo3.xml @@ -3,4 +3,3 @@ text notes. The latter three are converted to waypoints. Contributed by Curt Mills. - diff --git a/xmldoc/formats/unicsv.xml b/xmldoc/formats/unicsv.xml index 333baf0de..69e3f3f10 100644 --- a/xmldoc/formats/unicsv.xml +++ b/xmldoc/formats/unicsv.xml @@ -10,7 +10,7 @@ The list of keywords include: - + alt = Elevation (in meters) of the point. Add "ft" or "feet" for feet. arch = Geocache archived flag avail = Geocache available flag @@ -78,9 +78,9 @@ gpx, gdb, garmin_gpi and partly garmin_txt. These entities are currently - not visible in MapSource (6.12.4), but are NOT dropped + not visible in MapSource (6.12.4), but are NOT dropped when working with GDB (version 3) or GPX files. - + Please note, that these do NOT provide a geocoding service; don't expect to "convert" a street address to a latitude and longitude. @@ -97,28 +97,28 @@ A typical file may be: - + Name, Latitude, Longitude, Description GCEBB,35.972033,-87.134700,Mountain Bike Heaven by susy1313 GC1A37,36.090683,-86.679550,The Troll by a182pilot & Family - If processing data from the UK, GPSBabel can process coordinates using X,Y values (often referred to as Eastings/Northings) as shown in or the full 12 figure alpha numeric, as shown in . - Note in you need to split your original X,Y values into the 100Km 2 character code, + If processing data from the UK, GPSBabel can process coordinates using X,Y values (often referred to as Eastings/Northings) as shown in or the full 12 figure alpha numeric, as shown in . + Note in you need to split your original X,Y values into the 100Km 2 character code, eastings and northing values. - + CSV input for UK data with XY coordinates - + bng_e,bng_n,name,date 353729,177210,id_001,2018/02/03 356025,181221,id_002,2018/02/03 357962,181528,id_003,2018/03/03 - + CSV input for UK data with alphanumeric coordinates - + bng_z,bng_e,bng_n,name,date ST,53729,77210,id_001,2018/02/03 ST,56025,81221,id_002,2018/02/03 @@ -132,7 +132,7 @@ With at least ONE valid timestamp in data a unicsv output may look like that: - + No,Name,Latitude,Longitude,Description,Date,Time 1,"GCEBB",35.972033,-87.134700,"Mountain Bike Heaven by susy1313",2003/06/29,09:00:00 2,"GC1A37",36.090683,-86.679550,"The Troll by a182pilot & Family",, diff --git a/xmldoc/formats/v900.xml b/xmldoc/formats/v900.xml index 0124e11d8..0958f25c9 100644 --- a/xmldoc/formats/v900.xml +++ b/xmldoc/formats/v900.xml @@ -1,12 +1,12 @@ -Read-only support for the csv file format used by Visiontac VGPS-900 and Columbus V-900 GPS data loggers. These seem to be two brand names for the exact same product. +Read-only support for the csv file format used by Visiontac VGPS-900 and Columbus V-900 GPS data loggers. These seem to be two brand names for the exact same product. The the V-900 stores logs on a microSD card in a custom csv format. This format contains NULL characters and fixed length fields, and therefore can not be handled by the normal csv module in GPSBabel. -Visiontac VGPS-900 +Visiontac VGPS-900 - + Conversion of a v900 csv log file to a gpx format gpsbabel -i v900 -f 09040400.csv -o gpx -F outfile.gpx @@ -19,8 +19,7 @@ The device support logging of trackpoints, waypoints, and voice recordings (.wav If you happen to use this for OpenStreetMap.org project, you can easily click on a waypoint and open the wav file from within JOSM. For this you must use gpx version 1.1 as the output file. The next example shows exactly how to do that. - + Conversion of a v900 csv log file to a gpx 1.1 format gpsbabel -i v900 -f 09040400.csv -o gpx,gpxver=1.1 -F outfile.gpx - diff --git a/xmldoc/formats/vcard.xml b/xmldoc/formats/vcard.xml index 6e76b032d..2b0447734 100644 --- a/xmldoc/formats/vcard.xml +++ b/xmldoc/formats/vcard.xml @@ -10,4 +10,3 @@ into the iPod 'Contacts' folder. As an alternative, Mac OS X users may prefer to drag the VCF file into their address book and synchronize with the iPod using iSync. - diff --git a/xmldoc/formats/wbt-bin.xml b/xmldoc/formats/wbt-bin.xml index 867822664..3d3839b8c 100644 --- a/xmldoc/formats/wbt-bin.xml +++ b/xmldoc/formats/wbt-bin.xml @@ -1,12 +1,11 @@ -File protocol for the Wintec WBT-200 -and Wintec WBT-201 (sometimes called the G-Rays 2)GPS data loggers. This format reads the binary file format created +File protocol for the Wintec WBT-200 +and Wintec WBT-201 (sometimes called the G-Rays 2)GPS data loggers. This format reads the binary file format created by Wintec's Windows application. -Wintec WBT-201 +Wintec WBT-201 - + Command showing conversion of a Wintec binary file to GPX gpsbabel -i wbt-bin -f tracks.bin -o gpx -F out.gpx - diff --git a/xmldoc/formats/wbt-tk1.xml b/xmldoc/formats/wbt-tk1.xml index 4fba4bca0..f3d0c0222 100644 --- a/xmldoc/formats/wbt-tk1.xml +++ b/xmldoc/formats/wbt-tk1.xml @@ -1,11 +1,10 @@ -File protocol for the Wintec WBT-201 / G-Rays 2 +File protocol for the Wintec WBT-201 / G-Rays 2 GPS data logger. This format reads the binary file format created by Wintec's Time Machine X application. -Wintec WBT-201 +Wintec WBT-201 - + Command showing conversion of a Wintec binary file to GPX gpsbabel -w -t -i wbt-tk1 -f tracks.tk1 -o gpx -F out.gpx - diff --git a/xmldoc/formats/wbt.xml b/xmldoc/formats/wbt.xml index 2e5f08a96..8205d64f0 100644 --- a/xmldoc/formats/wbt.xml +++ b/xmldoc/formats/wbt.xml @@ -1,12 +1,12 @@ Serial download protocol for the -Wintec WBT-200 and -Wintec WBT-201 -Wintec WBT-1000 +Wintec WBT-200 and +Wintec WBT-201 +Wintec WBT-1000 GPS data loggers. Although untested it is expected that this will also support the WBT-100. -Wintec WBT-201 +Wintec WBT-201 - + Command showing WBT-200 download and erase over Bluetooth on Mac OS X gpsbabel -t -w -i wbt,erase -f /dev/cu.WBT200-SPPslave-1 -o gpx -F out.gpx @@ -16,12 +16,12 @@ Internally, this is actually a serial device that has a serial/USB adapter built into it. It uses the CP210x chip by Silicon labs. You will probably need a driver for this chip. The product ships with one for Windows. The Linux 210x driver seems to work fine. Mac users will need to download -the Mac driver for CP210x. +the Mac driver for CP210x. GPSBabel does not try to offer an interface to configure these units. That is left to the Windows software that comes with it or tools like the -WBT 201 Viewer for Mac OS/X +WBT 201 Viewer for Mac OS/X and Linux. diff --git a/xmldoc/formats/xcsv.xml b/xmldoc/formats/xcsv.xml index 88f55dfef..283cb719b 100644 --- a/xmldoc/formats/xcsv.xml +++ b/xmldoc/formats/xcsv.xml @@ -11,4 +11,3 @@ with the obvious exception of the option. Those formats are all based on style files that can be found in the "style" directory in the GPSBabel source distribution. - diff --git a/xmldoc/makedoc b/xmldoc/makedoc index 9c8a1049e..479e39f61 100755 --- a/xmldoc/makedoc +++ b/xmldoc/makedoc @@ -76,13 +76,21 @@ sub include { my $d2 = $dir2; $d2 =~ s:/.*::; $name2 = $d2 . '_' . $name2; - print $parts qq(\n); - print $file "\&inc_$name2;\n"; + + #print $parts qq(\n); + #print $file "\&inc_$name2;\n"; if ( !-e "$dir/$dir2/$name.xml" ) { - open my $tmp, '>', "$dir/$dir2/$name.xml" or die $!; + open my $tmp, '>:encoding(UTF-8)', "$dir/$dir2/$name.xml" or die $!; print $tmp "\n"; close $tmp; } + open my $tmp2, '<:encoding(UTF-8)', "$dir/$dir2/$name.xml" or die $!; + print $file qq(\n); + while (<$tmp2>) { + print $file $_; + } + print $file qq(\n); + close $tmp2; } sub includef { @@ -100,12 +108,12 @@ qx(mkdir -p $dir/autogen); if ( $? != 0 ) { die "error creating autogen directory: $?"; } -open $parts, '>', "$dir/autogen/_parts.xml" or die $!; +open $parts, '>:encoding(UTF-8)', "$dir/autogen/_parts.xml" or die $!; print $parts qq(\n); print $parts qq(\n); print $parts qq(\n); -open $formats, '>', "$dir/autogen/_formats.xml" or die $!; +open $formats, '>:encoding(UTF-8)', "$dir/autogen/_formats.xml" or die $!; print $formats qq(\n); my @formats = qx(./gpsbabel -^3); @@ -186,10 +194,10 @@ for (@formats) { $fmts{$id} = 1; } includef( 'fmt_' . $id ); - open $file, '>', "$dir/autogen/fmt_$id.xml" or die $!; + open $file, '>:encoding(UTF-8)', "$dir/autogen/fmt_$id.xml" or die $!; print $file < -
+
$line[4] ($line[2]) END print $file expandoptions( $line[1] ); @@ -213,7 +221,7 @@ END elsif ( $going && $dooptions && ( $line[0] eq 'option' ) ) { my $nid = 'fmt_' . $id . '_o_' . $line[2]; print $file < +
<option>$line[2]</option> option $line[3]. @@ -233,7 +241,7 @@ if ($going) { } close $formats; -open $formats, '>', "$dir/autogen/_filters.xml" or die $!; +open $formats, '>:encoding(UTF-8)', "$dir/autogen/_filters.xml" or die $!; print $formats qq(\n); my @filters = qx(./gpsbabel -%1); @@ -252,7 +260,7 @@ for (@filters) { if ( $going && ( $line[0] eq 'option' ) ) { print $file < +
$line[2] option $line[3]. @@ -269,10 +277,10 @@ END close $file; } includef( 'filter_' . $line[0] ); - open $file, '>', "$dir/autogen/filter_$line[0].xml" or die $!; + open $file, '>:encoding(UTF-8)', "$dir/autogen/filter_$line[0].xml" or die $!; print $file < -
+
$line[1] ($line[0]) END include( $line[0], "filters" ); diff --git a/xmldoc/readme.xml b/xmldoc/readme.xml index e46f2df11..18a0efb70 100644 --- a/xmldoc/readme.xml +++ b/xmldoc/readme.xml @@ -1,7 +1,5 @@ - - %parts; @@ -9,11 +7,8 @@ %chaps; ] > - - - - GPSBabel Documentation - + + GPSBabel Documentation &allchapters; diff --git a/xmldoc/tmissue.xsl b/xmldoc/tmissue.xsl new file mode 100644 index 000000000..eb50696c1 --- /dev/null +++ b/xmldoc/tmissue.xsl @@ -0,0 +1,11 @@ + + + + + + + + + + + -- 2.30.2